Alright, let's think this through logically. If the data is encrypted on the device that consumes the API (option A), that doesn't protect it during transmission. And encrypting on the server (option D) doesn't cover the end-to-end part. B is the only choice that ensures the data is secure from start to finish.
You know, I was thinking option C at first, but the question specifically asks about 'end-to-end' encryption. Encrypting on the end device after the request is received doesn't really cover the entire journey. B is the way to go.
I agree with Carey. Encrypting on the source device seems like the safest bet. That way, the data is protected from the moment it leaves the device until it reaches its final destination. Option B is my pick.
Hmm, this is a tricky one. End-to-end encryption is crucial, but where exactly should the data be encrypted? I'm leaning towards option B, encrypting on the source device before transmission. That way, the data is secure throughout the entire process.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Han
8 months agoToshia
8 months agoVeta
8 months agoRasheeda
8 months agoCarmen
8 months agoAlesia
8 months agoDulce
8 months agoAretha
8 months agoNgoc
8 months agoMarisha
8 months agoCarey
8 months ago