Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

Cisco 350-401 Exam - Topic 4 Question 111 Discussion

Actual exam question for Cisco's 350-401 exam

Question #: 111
Topic #: 4

[All 350-401 Questions]

Which method ensures the confidentiality of data exchanged over a REST API?

AUse TLS to secure the underlying HTTP session.

BUse me POST method Instead or URL-encoded GET to pass parameters.

CDeploy digest-based authentication to protect the access to the API.

DEncode sensitive data using Base64 encoding.

Show Suggested Answer

Suggested Answer: A

by Talia at Jul 08, 2025, 11:00 PM

Limited Time Offer

25%

Off

Get Premium 350-401 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Norah

9 months ago

A is the best choice, no doubt about it.

upvoted 0 times

...

Cassi

9 months ago

I think C is also important for API security.

upvoted 0 times

...

Renea

9 months ago

I thought using POST was enough, but I guess not?

upvoted 0 times

...

Brice

9 months ago

Wait, Base64 encoding? That's not secure at all!

upvoted 0 times

...

Clarence

9 months ago

Definitely A, TLS is a must for secure data.

upvoted 0 times

...

Gail

10 months ago

Base64 encoding seems like a weak option for confidentiality; I recall it just obfuscates data rather than encrypting it.

upvoted 0 times

...

Bernardine

10 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.

upvoted 0 times

...

Julian

10 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.

upvoted 0 times

...

Doyle

10 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.

upvoted 0 times

...

Royal

11 months 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.

upvoted 0 times

...

Louvenia

11 months 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.

upvoted 0 times

...

Colby

11 months 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.

upvoted 0 times

...

Dong

11 months ago

This looks like a straightforward security question. I'm pretty confident that the answer is A - using TLS to secure the HTTP session.

upvoted 0 times

...

Tricia

1 year ago

As a security expert, I can say with confidence that A is the correct answer. The others are just gimmicks.

upvoted 0 times

...

Alaine

1 year ago

Haha, Base64 encoding? That's like putting a sticky note on your front door. A is the only sensible choice.

upvoted 0 times

...

Miesha

1 year ago

B? Really? That's just security through obscurity. A is the clear winner here.

upvoted 0 times

Luisa

11 months ago

A? Really? That's just security through obscurity. B is the clear winner here.

upvoted 0 times

...

Dorethea

12 months ago

B) Use me POST method Instead or URL-encoded GET to pass parameters.

upvoted 0 times

...

Remona

12 months ago

A) Use TLS to secure the underlying HTTP session.

upvoted 0 times

...

...

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.

upvoted 0 times

Aja

1 year ago

TLS is definitely the way to go for securing data over a REST API.

upvoted 0 times

...

Malcom

1 year ago

I agree, using TLS is a common and effective way to ensure data confidentiality.

upvoted 0 times

...

...

Candra

1 year ago

I believe A) is the correct answer because TLS provides end-to-end encryption for data security.

upvoted 0 times

...

Rex

1 year ago

I'm not sure, but I think C) Deploy digest-based authentication could also work.

upvoted 0 times

...

Joaquin

1 year ago

Definitely option A. TLS is the way to go for secure data exchange over REST APIs.

upvoted 0 times

Ngoc

1 year ago

A) Use TLS to secure the underlying HTTP session.

upvoted 0 times

...

Marla

1 year ago

C) Deploy digest-based authentication to protect the access to the API.

upvoted 0 times

...

German

1 year ago

A) Use TLS to secure the underlying HTTP session.

upvoted 0 times

...

...

Jacquelyne

1 year ago

I agree with Laura, TLS encryption is the best way to ensure confidentiality.

upvoted 0 times

...

Laura

1 year ago

I think the answer is A) Use TLS to secure the underlying HTTP session.

upvoted 0 times

...