hardMultiple Choice
CCSP Practice Question: An Azure application uses a key vault key for…
Exhibit
Refer to the exhibit.
```
$ az keyvault key list --vault-name myVault
[
{
"kid": "https://myVault.vault.azure.net/keys/myKey/abc123",
"attributes": {
"enabled": true,
"created": 1590000000,
"updated": 1590000000
},
"tags": {
"usage": "encryption"
}
}
]
$ openssl s_client -connect myserver.cloudapp.net:443 -servername myserver.cloudapp.net
CONNECTED(00000003)
140735123456:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:s3_pkt.c:1487:SSL alert number 40
```An Azure application uses a key vault key for client-side encryption of data. The application also communicates with a cloud service over HTTPS. After deploying, the handshake failure occurs. Which of the following is the most likely cause?
⚠ Common exam trap
Test-takers frequently confuse client-side encryption (using a key vault key) with transport-layer security (TLS), assuming a key-related issue causes the handshake failure, when in fact the handshake is a separate protocol layer.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The client and server do not have a common TLS version or cipher suite
The handshake failure occurs at the transport layer (TLS/SSL), which is independent of client-side encryption using a key vault key. The most likely cause is a mismatch in TLS versions or cipher suites between the client and server, as HTTPS relies on a successful TLS handshake. Options A, B, and D relate to the key vault key's availability or configuration, which would not cause a TLS handshake failure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The application is using the wrong key version
Why it's wrong here
A wrong key version breaks client-side encryption or decryption of data, not the TLS handshake with the cloud service. Key versioning matters when rotating keys and an application still references a retired version, causing cryptographic operation failures rather than connection negotiation errors.
- ✗
The key vault key is not accessible due to network restrictions
Why it's wrong here
Network restrictions on the vault block access to key operations, producing encryption or decryption failures, not the TLS handshake with the cloud service. This would be correct if the application could not retrieve keys at all, causing key-retrieval timeouts during cryptographic operations.
- ✓
The client and server do not have a common TLS version or cipher suite
Why this is correct
A TLS handshake failure arises from mismatched protocol versions or cipher suites between client and server, not from the key vault key used for client-side data encryption. Since the stem specifies HTTPS communication, the negotiation failure points to incompatible TLS parameters, making this the most likely cause.
- ✗
The key vault key is not enabled for encryption
Why it's wrong here
Encryption key enablement governs cryptographic operations on stored data, not the TLS negotiation that produces a handshake failure. Disabling a key would cause decryption errors, not connection failure. This option would be correct if the application reported key-operation failures during client-side encryption.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CCSP question from scratch — 934 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CCSP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCSP exam.