Which statement best contrasts symmetric and asymmetric cryptography and cites a representative use case?

Which statement best contrasts symmetric and asymmetric cryptography and cites a representative use case?

• A. Symmetric uses the same key for encryption and decryption; asymmetric uses the same key for encryption and decryption.
• B. Symmetric uses the same key for encryption and decryption; asymmetric uses public/private keys; example: TLS handshake uses asymmetric keys to establish a session and then symmetric keys for data transfer.
• C. Symmetric uses public keys; asymmetric uses private keys.
• D. Symmetric uses private keys; asymmetric uses public keys; TLS uses private keys for session establishment.

Answer: (B)

The main idea is that symmetric and asymmetric cryptography serve different roles based on how keys are used. Symmetric encryption uses the same secret key to both encrypt and decrypt, which makes it fast for handling large amounts of data but requires securely sharing that key in advance. Asymmetric encryption uses a key pair—a public key that can be shared openly and a private key that stays secret—so encryption (or verification) can be done with the public key while decryption (or signing) uses the private key, removing the need to exchange a secret key upfront and enabling trust-building and secure key exchange, though at a slower pace. A representative use case that illustrates this contrast is the TLS handshake. During the handshake, asymmetric cryptography is used to authenticate the server and securely exchange information that allows both sides to agree on a symmetric session key. Once that session key is established, the actual data transferred during the session is encrypted with symmetric keys for speed and efficiency. This combination shows how asymmetric cryptography handles secure setup and trust, while symmetric cryptography handles the bulk data encryption. The other statements don’t fit because they misstate how keys are used. One claim says the same key is used for encryption and decryption in both schemes, which isn’t true for asymmetric cryptography. Another reverses the key roles by saying symmetric uses public keys and asymmetric uses private keys. The remaining statement about TLS oversimplifies and implies private keys alone drive session establishment, omitting the public/private key dynamic and the subsequent symmetric encryption stage.

The main idea is that symmetric and asymmetric cryptography serve different roles based on how keys are used. Symmetric encryption uses the same secret key to both encrypt and decrypt, which makes it fast for handling large amounts of data but requires securely sharing that key in advance. Asymmetric encryption uses a key pair—a public key that can be shared openly and a private key that stays secret—so encryption (or verification) can be done with the public key while decryption (or signing) uses the private key, removing the need to exchange a secret key upfront and enabling trust-building and secure key exchange, though at a slower pace.

A representative use case that illustrates this contrast is the TLS handshake. During the handshake, asymmetric cryptography is used to authenticate the server and securely exchange information that allows both sides to agree on a symmetric session key. Once that session key is established, the actual data transferred during the session is encrypted with symmetric keys for speed and efficiency. This combination shows how asymmetric cryptography handles secure setup and trust, while symmetric cryptography handles the bulk data encryption.

The other statements don’t fit because they misstate how keys are used. One claim says the same key is used for encryption and decryption in both schemes, which isn’t true for asymmetric cryptography. Another reverses the key roles by saying symmetric uses public keys and asymmetric uses private keys. The remaining statement about TLS oversimplifies and implies private keys alone drive session establishment, omitting the public/private key dynamic and the subsequent symmetric encryption stage.