Which method ensures the confidentiality of data exchanged over a REST API?
Suggested Answer: A
Get Premium 350-401 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
NO
Norah
10 months ago
A is the best choice, no doubt about it.
CA
Cassi
10 months ago
I think C is also important for API security.
RE
Renea
11 months ago
I thought using POST was enough, but I guess not?
BR
Brice
11 months ago
Wait, Base64 encoding? That's not secure at all!
CL
Clarence
11 months ago
Definitely A, TLS is a must for secure data.
GA
Gail
11 months ago
Base64 encoding seems like a weak option for confidentiality; I recall it just obfuscates data rather than encrypting it.
BE
Bernardine
11 months ago
I feel like digest-based authentication could help with security, but I’m not clear on how it specifically ensures confidentiality over data exchange.
JU
Julian
12 months ago
I remember practicing a question about REST APIs, and I think the POST method is more secure than GET, but I’m not sure it directly relates to confidentiality.
DO
Doyle
12 months ago
I think using TLS is definitely the right choice for ensuring confidentiality, but I’m not 100% sure if it’s the only method we should consider.
RO
Royal
1 year ago
I'm a bit confused by this question. Encoding data with Base64 doesn't really ensure confidentiality, since it's just obfuscation, not encryption. I'm leaning towards option A, but I want to make sure I understand the differences between the approaches before I commit to an answer.
LO
Louvenia
1 year ago
Okay, let's see. I think option B about using POST instead of GET is a good idea, but that's more about hiding sensitive data in the URL. Option C with digest-based authentication sounds promising, but I'm not sure if that's the best way to ensure confidentiality. I'll have to review my notes on REST API security.
CO
Colby
1 year ago
Hmm, I'm not sure about this one. I know that TLS is used to encrypt data, but I'm not sure if that's the only way to ensure confidentiality in a REST API. I'll have to think this through carefully.
DO
Dong
1 year ago
This looks like a straightforward security question. I'm pretty confident that the answer is A - using TLS to secure the HTTP session.
TR
Tricia
1 year ago
As a security expert, I can say with confidence that A is the correct answer. The others are just gimmicks.
AL
Alaine
1 year ago
Haha, Base64 encoding? That's like putting a sticky note on your front door. A is the only sensible choice.
MI
Miesha
1 year ago
B? Really? That's just security through obscurity. A is the clear winner here.
LU
Luisa
1 year ago
A? Really? That's just security through obscurity. B is the clear winner here.
DO
Dorethea
1 year ago
B) Use me POST method Instead or URL-encoded GET to pass parameters.
RE
Remona
1 year ago
A) Use TLS to secure the underlying HTTP session.
LA
Lai
1 year ago
I'm torn between A and C. Both seem like viable options, but I think I'll go with A for its simplicity and wide adoption.
AJ
Aja
1 year ago
TLS is definitely the way to go for securing data over a REST API.
MA
Malcom
1 year ago
I agree, using TLS is a common and effective way to ensure data confidentiality.
CA
Candra
1 year ago
I believe A) is the correct answer because TLS provides end-to-end encryption for data security.
RE
Rex
1 year ago
I'm not sure, but I think C) Deploy digest-based authentication could also work.
JO
Joaquin
1 year ago
Definitely option A. TLS is the way to go for secure data exchange over REST APIs.
NG
Ngoc
1 year ago
A) Use TLS to secure the underlying HTTP session.
MA
Marla
1 year ago
C) Deploy digest-based authentication to protect the access to the API.
GE
German
1 year ago
A) Use TLS to secure the underlying HTTP session.
JA
Jacquelyne
1 year ago
I agree with Laura, TLS encryption is the best way to ensure confidentiality.
LA
Laura
1 year ago
I think the answer is A) Use TLS to secure the underlying HTTP session.