📝 SSL architecture in computer networks (18 MCQs)

📖 From Data Communication and Networks • 32. Internet Security • 18 questions available

←Previous Topic:SSL TLS transport layer security📝 SSL architecture in computer networksSSL protocols handshake record change cipher alert:Next Topic→

What is SSL architecture in computer networks?

The SSL/TLS architecture consists of two primary layers: the Record Protocol, which handles fragmentation, compression, encryption, and integrity checking, and multiple handshake protocols that manage session establishment and key exchange.

Easy

Medium

Hard

📝 All SSL architecture in computer networks MCQs

Q1. If the server's certificate is invalid, which step in the SSL handshake will fail?

A.ClientHello

B.CertificateVerify ✅

C.ServerHello

D.Finished

💡 Difficulty: easy | ✅ Correct: B

📖 Explanation: The CertificateVerify message is sent by the client to prove possession of the private key that matches its certificate. An invalid server certificate prevents the client from generating a valid CertificateVerify, causing the handshake to abort at that point, while earlier messages like ClientHello and ServerHello are still exchanged.

Q2. During an SSL session, if the client receives a ChangeCipherSpec before ServerHello, what can be inferred?

A.The server is using an outdated protocol version

B.The handshake is proceeding normally

C.The client has prematurely terminated the connection

D.A protocol anomaly indicating a possible attack or misconfiguration ✅

💡 Difficulty: medium | ✅ Correct: D

📖 Explanation: Receiving ChangeCipherSpec before ServerHello violates the prescribed message order defined in the TLS specification. This out‑of‑sequence message suggests either a misconfigured implementation or an active attempt to confuse the client, both of which are abnormal and warrant termination of the session.

Q3. Suppose a man‑in‑the‑middle strips SSL, causing the client to fall back to HTTP. Which sequence best describes the resulting security breach?

A.Client sends HTTP request → attacker reads data → response sent in clear ✅

B.Client sends HTTPS request → attacker downgrades to HTTP → attacker reads data

C.Client negotiates TLS 1.3 → attacker blocks handshake → client aborts

D.Server sends encrypted data → attacker cannot decrypt

💡 Difficulty: hard | ✅ Correct: A

📖 Explanation: When SSL is stripped, the client believes it is using HTTPS, but the request is sent over plain HTTP. The attacker intercepts the unencrypted request and response, gaining full visibility of the payload. This downgrade attack undermines confidentiality and integrity that SSL is designed to protect.

Q4. If a server supports both TLS 1.2 and TLS 1.3, and the client offers only TLS 1.2, what handshake outcome is expected?

A.TLS 1.3 will be forced by the server

B.Handshake will fail due to version mismatch

C.TLS 1.2 will be negotiated and used ✅

D.Both versions will be used simultaneously

💡 Difficulty: medium | ✅ Correct: C

📖 Explanation: The TLS version negotiation selects the highest version supported by both parties. Since the client only offers TLS 1.2, the server will downgrade to TLS 1.2, completing the handshake with that version. No failure occurs because the server still supports the client’s offered version.

Q5. When forward secrecy is enabled, which key exchange algorithm ensures that compromise of the server's private key does not expose past session keys?

A.RSA

B.ECDHE ✅

C.DHE

D.PSK

💡 Difficulty: hard | ✅ Correct: B

📖 Explanation: Elliptic Curve Diffie‑Hellman Ephemeral (ECDHE) generates a temporary key pair for each session. Even if the server's long‑term private key is later compromised, the ephemeral private key used for that session is discarded, so past session keys remain undisclosed, providing forward secrecy.

Q6. If the client aborts after receiving ServerHelloDone, which SSL handshake message is most likely missing?

A.Finished

B.CertificateVerify

C.ChangeCipherSpec

D.Alert ✅

💡 Difficulty: easy | ✅ Correct: D

📖 Explanation: The ServerHelloDone signals the end of the server's initial messages. The client typically follows with its own Certificate, ClientKeyExchange, then ChangeCipherSpec and Finished. An abrupt abort after ServerHelloDone usually indicates the client never sent the ChangeCipherSpec, which is required before the Finished message.

Q7. Compare the number of round‑trips in the classic SSL handshake with the TLS 1.3 handshake. Which statement is accurate?

A.SSL requires two round‑trips; TLS 1.3 requires one ✅

B.SSL requires one round‑trip; TLS 1.3 requires two

C.Both require two round‑trips

D.Both require one round‑trip

💡 Difficulty: easy | ✅ Correct: A

📖 Explanation: The classic SSL/TLS handshake (pre‑TLS 1.3) involves a ClientHello, ServerHello, certificate exchange, and Finished messages, resulting in two full round‑trips. TLS 1.3 streamlines the process by combining many steps into the initial messages, reducing the exchange to a single round‑trip.

Q8. Evaluate the impact of disabling RSA key exchange on client compatibility. Which outcome is most likely?

A.All modern browsers will still connect

B.Only browsers that support only RSA will fail

C.Compatibility remains unchanged for all clients ✅

D.Only servers will be affected, not clients

💡 Difficulty: medium | ✅ Correct: C

📖 Explanation: Disabling RSA key exchange forces the use of Diffie‑Hellman‑based suites (DHE/ECDHE). Modern browsers support these suites, so they continue to connect. However, legacy clients that only implement RSA key exchange will be unable to negotiate a cipher suite, leading to connectivity issues for those outdated devices.

Q9. Differentiate MAC‑then‑encrypt from encrypt‑then‑MAC in SSL. Which statement best captures their security difference?

A.MAC‑then‑encrypt prevents padding oracle attacks, encrypt‑then‑MAC does not

B.Encrypt‑then‑MAC provides better integrity guarantees because the MAC covers ciphertext ✅

C.Both approaches offer identical security properties

D.MAC‑then‑encrypt is always preferred for performance reasons

💡 Difficulty: hard | ✅ Correct: B

📖 Explanation: Encrypt‑then‑MAC computes the MAC over the ciphertext, ensuring that any alteration of the ciphertext is detected before decryption, which prevents certain attacks. In MAC‑then‑encrypt, the MAC is computed on the plaintext, and an attacker could manipulate the ciphertext without immediate detection, making it less secure.

Q10. Compare session resumption using session IDs versus session tickets. Which advantage belongs to session tickets?

A.Tickets reduce server memory usage

B.Tickets require the server to store more state

C.Session IDs enable faster handshakes than tickets

D.Tickets eliminate the need for client-side storage ✅

💡 Difficulty: medium | ✅ Correct: D

📖 Explanation: Session tickets encapsulate the session state in an encrypted blob that the client stores and returns, allowing the server to resume the session without maintaining per‑client state. This reduces server memory consumption and simplifies scaling, whereas session IDs rely on server‑side storage of session data.

Q11. Analyze the effect of certificate pinning on mitigating man‑in‑the‑middle attacks. Which outcome is most accurate?

A.Pinning eliminates the need for TLS entirely

B.Pinning ensures the client only trusts a specific certificate or public key, reducing attack surface

C.Pinning makes handshake faster by skipping verification ✅

D.Pinning has no impact on security, only on performance

💡 Difficulty: hard | ✅ Correct: C

📖 Explanation: Certificate pinning restricts the set of trusted certificates to a known good value. If an attacker presents a fraudulent certificate, the client will reject it, thereby mitigating many MITM scenarios. However, pinning does not affect handshake speed; it adds a verification step.

Q12. Contrast the use of static Diffie‑Hellman versus ephemeral Diffie‑Hellman in SSL. Which statement correctly describes the difference?

A.Static DH provides forward secrecy, ephemeral DH does not

B.Ephemeral DH generates a new key pair each session, offering forward secrecy ✅

C.Static DH requires more computational resources than ephemeral DH

D.Both use the same key material, differing only in naming

💡 Difficulty: easy | ✅ Correct: B

📖 Explanation: Ephemeral Diffie‑Hellman (DHE/ECDHE) creates a fresh key pair for each session, ensuring that even if the server’s long‑term private key is compromised, past session keys remain secret. Static DH reuses the same parameters, lacking forward secrecy.

Q13. How does the Finished message provide integrity assurance in an SSL/TLS session?

A.It contains a hash of all previous handshake messages encrypted with the session key ✅

B.It sends the session key in clear text

C.It only confirms that the server is alive

D.It includes a random nonce without any cryptographic binding

💡 Difficulty: medium | ✅ Correct: A

📖 Explanation: The Finished message includes a MAC computed as $\text{MAC}=H(\text{handshake\_messages} \parallel \text{master\_secret})$ . This MAC, encrypted with the newly derived keys, proves that both parties have the same view of the handshake, guaranteeing integrity and authenticity of the entire exchange.

Q14. Design a secure configuration that mitigates the POODLE attack. Which combination is most effective?

A.Enable SSL 3.0, disable CBC ciphers, use RC4

B.Disable SSL 3.0, enable TLS 1.2, disallow CBC mode

C.Enable TLS 1.3 only, allow all ciphers, keep SSL 3.0 disabled

D.Use only SSL 3.0 with strong ciphers ✅

💡 Difficulty: hard | ✅ Correct: D

📖 Explanation: The POODLE attack exploits SSL 3.0's padding vulnerability. The safest mitigation is to disable SSL 3.0 entirely, enforce TLS 1.3 (which removes CBC padding issues), and permit only modern, secure cipher suites. This configuration eliminates the vulnerable protocol and cipher interactions.

Q15. Explain the relationship between cipher suite selection and performance in SSL. Which statement is true?

A.Stronger ciphers always increase latency regardless of hardware

B.Choosing a suite with hardware‑accelerated algorithms can improve throughput without sacrificing security ✅

C.Cipher suites have no impact on performance, only on security

D.Weaker ciphers always provide better performance but are insecure

💡 Difficulty: medium | ✅ Correct: B

📖 Explanation: Modern CPUs often include acceleration for AES‑GCM and ChaCha20‑Poly1305. Selecting a cipher suite that leverages these hardware features can deliver high security while maintaining low latency and high throughput, whereas purely software‑based ciphers may incur higher CPU usage.

Q16. What role does the Alert protocol play in SSL/TLS error handling?

A.It encrypts application data

B.It signals warning or fatal conditions to the peer

C.It negotiates cipher suites ✅

D.It establishes the session key

💡 Difficulty: hard | ✅ Correct: C

📖 Explanation: The Alert protocol is a dedicated message type used to convey warning or fatal error conditions (e.g., unexpected_message, handshake_failure). Alerts are sent in plaintext or encrypted depending on the stage of the handshake, allowing each endpoint to react appropriately—either by attempting recovery or terminating the connection.

Q17. What does SSL stand for?

A.Secure Socket Layer

B.Secure System Link

C.Simple Secure Layer

D.Secure Sockets Layer ✅

💡 Difficulty: easy | ✅ Correct: D

📖 Explanation: SSL is an acronym for Secure Sockets Layer, the original protocol suite that provided encrypted communications over the Internet before being succeeded by TLS.

Q18. Which port is the default for HTTPS traffic?

A.443 ✅

B.80

C.21

D.25

💡 Difficulty: medium | ✅ Correct: A

📖 Explanation: HTTPS, the secure version of HTTP that typically runs over SSL/TLS, uses TCP port 443 by convention. Port 80 is used for plain HTTP, 21 for FTP, and 25 for SMTP.

🔗 Related Topics (MCQs)

📝 IPSec network layer security MCQs 📝 IPSec transport and tunnel modes: Two Modes MCQs 📝 IPSec AH and ESP Two Security Protocols MCQs 📝 IPSec security services MCQs 📝 Security Association in IPSec MCQs

←Previous Topic:SSL TLS transport layer security📝 SSL architecture in computer networksSSL protocols handshake record change cipher alert:Next Topic→