MENU
A developer is asked to implement a simple call to an authentication - protected REST web service.
Which configuration is valid?
Suggested Answer: A
Get Premium CCM-101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
CA
Carlton
11 months ago
I’m surprised this is even a question, isn’t it obvious?
ST
Staci
11 months ago
Wait, can you really just add the password like that?
HA
Hana
12 months ago
C is just for configuration, not authentication.
SH
Shonda
12 months ago
I think B makes more sense for security.
PE
Penney
12 months ago
A is definitely the way to go!
RE
Reuben
1 year ago
This question reminds me of a similar one we practiced, but I can't recall if we discussed the specifics of using site preferences for authentication.
VA
Vallie
1 year ago
I feel like option C could be relevant too, especially if the endpoint needs to be referenced in the code.
WA
Walton
1 year ago
I'm not entirely sure, but I remember something about site preferences in option B being used for configuration settings.
FR
Franklyn
1 year ago
I think option A might be correct since adding the password to the service credentials seems like a common practice for authentication.
DE
Denae
1 year ago
I think a multi-stage Dockerfile would be the best approach here. It allows you to build and test the application in a separate stage without publishing the results to the pipeline.
MA
Matthew
1 year ago
I'm a bit uncertain about this one. The $match stage seems straightforward, but the $group stage has me stumped. I'll need to think it through carefully before committing to an answer.
BO
Bobbye
1 year ago
Hmm, I'm not entirely sure about this one. I'll need to think through the SMTP protocol details to determine if the statement is true or false.
RO
Roxane
1 year ago
I bet the developer who came up with these options was the same one who thought it was a good idea to put the nuclear launch codes on a Post-it note.
LY
Lynelle
1 year ago
Wait, are we supposed to use the password as the secret decoder ring for the authentication? Silly me, I thought we were past the days of hiding secrets in plain sight.
PE
Pearly
1 year ago
C) Insert the service's endpoint in a .properties file.
RE
Reita
1 year ago
B) Configure the authentication username using a site preference.
MO
Mozell
1 year ago
A) Add the authentication password to the service credentials.
AN
Annelle
1 year ago
Stashing the endpoint in a .properties file? Classy move, keeps it nice and organized.
VA
Vashti
1 year ago
A: Definitely, makes it easier to manage the configurations.
HU
Hui
1 year ago
B: Yeah, it's a good way to keep everything neat and tidy.
HE
Heidy
1 year ago
A: C) Insert the service's endpoint in a .properties file.
DO
Dolores
1 year ago
Configuring the username through a site preference? Sounds like a good way to manage that sensitive info.
RO
Roslyn
2 years ago
Hmm, adding the password to the service credentials? That's a big no-no! Security 101, folks.
CH
Chun
1 year ago
C) Insert the service's endpoint in a .properties file.
ME
Melodie
1 year ago
Hmm, adding the password to the service credentials? That's a big no-no! Security 101, folks.
GL
Glendora
1 year ago
A) Add the authentication password to the service credentials.
JA
Jamie
2 years ago
But wouldn't it be more secure to keep the password separate from the credentials?
JO
Josphine
2 years ago
I disagree, I believe the authentication username should be configured using a site preference.
JA
Jamie
2 years ago
I think the correct configuration is to add the authentication password to the service credentials.