350-901 · Question #86
Why is end-to-end encryption deployed when exposing sensitive data through APIs?
The correct answer is C. Data cannot be read or modified other than by the true source and destination. End-to-end encryption ensures that sensitive data remains encrypted from the moment it leaves the sender until it reaches the final recipient, preventing unauthorized parties from reading or tampering with it during transit.
Question
Exhibit
Options
- ATraffic is encrypted and decrypted at every hop in the network path.
- BData transfers are untraceable from source to destination.
- CData cannot be read or modified other than by the true source and destination.
- DServer-side encryption enables the destination to control data protection.
How the community answered
(29 responses)- A3% (1)
- C93% (27)
- D3% (1)
Why each option
End-to-end encryption ensures that sensitive data remains encrypted from the moment it leaves the sender until it reaches the final recipient, preventing unauthorized parties from reading or tampering with it during transit.
This describes hop-by-hop encryption (e.g., TLS at each proxy), not end-to-end encryption, where data remains encrypted across hops.
End-to-end encryption is about data confidentiality and integrity, not making data transfers untraceable; network metadata (like source/destination IPs) is still visible.
End-to-end encryption ensures that data is encrypted at the source and remains encrypted across all intermediate points until it is decrypted only by the intended final destination, thus preventing any unauthorized entity, including intermediate network devices or services, from reading or modifying the data.
Server-side encryption typically refers to encryption at rest on the server; end-to-end encryption focuses on protecting data in transit from the client to the server and vice-versa, involving both ends.
Concept tested: Purpose of end-to-end encryption
Topics
Community Discussion
No community discussion yet for this question.
