Quick Answer
The answer is a TLS handshake failure due to version mismatch, not a cipher mismatch. This occurs because the server exclusively supports TLS 1.2, while the client is limited to TLS 1.0; during the handshake, the client’s ClientHello advertises version 1.0, and the server’s ServerHello responds with 1.2, but neither side can downgrade to a common version, so the connection aborts. On the Systems Security Certified Practitioner SSCP exam, this scenario tests your understanding of TLS protocol negotiation—specifically that version compatibility is checked before cipher suites are even compared. A common trap is assuming the handshake fails because of incompatible ciphers, but the real issue is that no shared TLS version exists. Remember the memory tip: “Version first, cipher second”—the handshake always negotiates the protocol version before selecting a cipher suite.
This SSCP practice question tests your understanding of cryptography. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An administrator reports that a TLS handshake fails between a web server and client. The server supports TLS 1.2 with ciphers ECDHE-RSA-AES128-GCM-SHA256 and RSA-AES256-CBC-SHA256. The client supports only TLS 1.0 with ciphers RSA-RC4-SHA and RSA-AES128-SHA. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Cipher suite order misconfiguration
Why wrong: Even if reordered, no common ciphers due to version.
Certificate validation failure
Why wrong: No indication of certificate issues.
No common TLS version
The server supports TLS 1.2 only; client only TLS 1.0.
No common cipher suite
Why wrong: Cipher mismatch is an issue but the root is TLS version.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
No common TLS version
The TLS handshake fails because the server supports only TLS 1.2, while the client supports only TLS 1.0. During the handshake, the client sends a ClientHello with its highest supported version (1.0), and the server responds with a ServerHello indicating its highest supported version (1.2). Since neither side can downgrade to a mutually supported version, the handshake aborts. This is a version negotiation failure, not a cipher mismatch.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Cipher suite order misconfiguration
Why it's wrong here
Even if reordered, no common ciphers due to version.
Certificate validation failure
Why it's wrong here
No indication of certificate issues.
No common TLS version
Why this is correct
The server supports TLS 1.2 only; client only TLS 1.0.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
No common cipher suite
Why it's wrong here
Cipher mismatch is an issue but the root is TLS version.
Common exam traps
The trap here is that candidates see different cipher suites and assume a cipher mismatch (Option D), but the real issue is that the TLS versions are incompatible, which is checked before cipher negotiation.
Detailed technical explanation
TLS version negotiation is defined in RFC 5246 (TLS 1.2) and RFC 2246 (TLS 1.0). The client advertises its highest supported version in the ClientHello, and the server responds with the highest mutually supported version in the ServerHello. If the server's highest version is lower than the client's lowest, or vice versa, the handshake fails with a 'protocol_version' alert. In practice, servers often disable older TLS versions (e.g., TLS 1.0) for security, while legacy clients may not support newer versions, causing this exact failure.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Cryptography — study guide chapter
Learn the concepts, then practise the questions
Cryptography practice questions
Targeted practice on this topic area only
All SSCP questions
504 questions across all exam domains
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
Practise SSCP questions linked to Network and Communications Security.
Practise SSCP questions linked to Systems and Application Security.
Practise SSCP questions linked to Security Operations and Administration.
Practise SSCP questions linked to Incident Response and Recovery.
Practise SSCP questions linked to Access Controls.
Practise SSCP questions linked to Cryptography.
Practise SSCP questions linked to SSCP fundamentals.
Practise SSCP questions linked to SSCP scenario.
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Cryptography — This question tests Cryptography — Read the scenario before looking for a memorised answer..
The correct answer is: No common TLS version — The TLS handshake fails because the server supports only TLS 1.2, while the client supports only TLS 1.0. During the handshake, the client sends a ClientHello with its highest supported version (1.0), and the server responds with a ServerHello indicating its highest supported version (1.2). Since neither side can downgrade to a mutually supported version, the handshake aborts. This is a version negotiation failure, not a cipher mismatch.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
This SSCP 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 SSCP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.