Which Protocol Securely Exchanges a Symmetric Key Over an Unsecured Channel?
Your company, SecureTech Inc., is planning to transmit some sensitive data over an unsecured communication channel. As a cyber security expert, you decide to use symmetric key encryption to protect the data. However, you must also ensure the secure exchange of the symmetric key. Which of the following protocols would you recommend to the team to achieve this?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of key-exchange mechanisms versus transport security protocols; the trap is picking a secure channel (HTTPS/SSL/SSH) instead of the protocol purpose-built for agreeing on a symmetric key.
When symmetric encryption protects data on an unsecured channel, the remaining problem is agreeing on the shared key without exposing it, which is exactly what the Diffie-Hellman key exchange solves. This page confirms D as the correct answer and explains why HTTPS, SSL certificates, and SSH do not directly address symmetric key distribution.
Option A is the most tempting distractor — learners assume HTTPS alone solves the problem, but HTTPS secures a session via TLS handshake rather than providing the key-exchange primitive you apply to an arbitrary symmetric key over an untrusted link.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Diffie-Hellman is an asymmetric key-exchange algorithm whose sole purpose is to let two parties derive a shared secret over an untrusted channel without ever transmitting that secret, which is precisely the "secure exchange of the symmetric key" requirement in the SecureTech scenario. Each side contributes a public value, and both compute the identical session key mathematically, so eavesdroppers observing the public values cannot recover the shared secret (absent a compromise of a discrete-log hard problem). This makes D the only option that directly addresses symmetric key distribution rather than just protecting traffic.Why the Other Options Are Wrong
Option A (HTTPS) wraps web traffic in TLS, but TLS itself relies on a key-exchange mechanism underneath — it does not replace the need to establish how a symmetric key is agreed upon for your specific data. Option B (SSL certificates) is only a server-authentication and trust-anchor component; certificates prove identity but do not perform symmetric key exchange. Option C (SSH) secures interactive remote login sessions, which is a different use case than distributing a symmetric key for protecting data over an unsecured channel.Community Comment Notes
The community unanimously chose D. As insaniunt noted, Diffie-Hellman "is specifically designed for securely exchanging cryptographic keys over an untrusted communication channel," and LordXander echoed that once the stem asks to "ensure the secure exchange of the symmetric key," "the only one applicable is D." A removed commenter asked for confirmation, and the vote distribution plus the cryptography doctrine both support the unanimous verdict.Official Reference
Exam Strategy
Read the stem's final constraint carefully — here it is key exchange, not channel security — and match it to the protocol whose primary function that is. In EC-Council cryptography questions, Diffie-Hellman is the recurring answer whenever secure symmetric key distribution over an untrusted medium is the stated goal.
Frequently Asked Questions
Why is HTTPS not sufficient for exchanging a symmetric key?
HTTPS protects web sessions via TLS, which internally still depends on a key-exchange mechanism; it is a channel solution, not a standalone symmetric key-distribution protocol.
Do SSL certificates perform symmetric key exchange?
No. SSL/TLS certificates authenticate server identity and anchor trust; the actual key agreement is handled by algorithms such as Diffie-Hellman inside the handshake.