CND Practice Question: Network Security Controls Protocols And Devices
A network engineer is configuring TLS 1.3 on an enterprise load balancer. During cipher suite selection, the engineer observes that cipher suites like TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 are no longer listed in the configuration menu. What is the primary reason for this change in TLS 1.3?
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
✓
TLS 1.3 separates key exchange parameters from cipher suites, simplifying options to AEAD algorithms
TLS 1.3 decouples key exchange algorithms from authentication algorithms and removes obsolete static RSA and static DH cipher suites, supporting only AEAD (Authenticated Encryption with Associated Data) ciphers and modern key exchange methods.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
TLS 1.3 separates key exchange parameters from cipher suites, simplifying options to AEAD algorithms
Why this is correct
TLS 1.3 restructured cipher suites so that key exchange is negotiated independently, and only authenticated encryption with associated data (AEAD) ciphers are permitted.
- ✗
TLS 1.3 eliminates symmetric encryption in favor of asynchronous cryptographic operations for all data payloads
Why it's wrong here
Symmetric encryption (such as AES-GCM) is still used for bulk data transfer in TLS 1.3 due to performance efficiency; asymmetric cryptography is only used during the handshake.
- ✗
TLS 1.3 requires all connections to use legacy RSA key transport mechanisms
Why it's wrong here
Legacy RSA key transport was removed in TLS 1.3 because it lacks forward secrecy.
- ✗
TLS 1.3 mandates the use of pre-shared keys (PSKs) exclusively for all sessions
Why it's wrong here
While TLS 1.3 supports PSKs, it does not mandate them exclusively; certificate-based authentication is still widely used.
Quick reference
Asymmetric Encryption Algorithm Comparison
| Algorithm | Key Exchange | Signatures | Equivalent Security Key | Notes |
|---|---|---|---|---|
| RSA-3072 | Yes | Yes | 128-bit | Widely deployed; slow for bulk data |
| ECDSA P-256 | No | Yes | 128-bit | Fast signatures; standard TLS certs |
| ECDH / ECDHE | Yes | No | 128-bit | Perfect forward secrecy in TLS 1.3 |
| DH / DHE | Yes | No | 128-bit (3072-bit key) | Replaced by ECDHE in modern TLS |
| Ed25519 | No | Yes | ~128-bit | SSH keys, modern PKI |
About these practice questions
One of 323 original CND practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official EC-Council exam blueprint
This CND practice question is part of Courseiva's free EC-Council 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 CND exam.