MENU
You need to access API back-end systems authorized by a machine user credential Each API call must connect to the API back-end system with unique credentials You need to keep user credential info securely protected How should you store the credential?
Suggested Answer: D
Get Premium Google Cloud - Apigee Certified API Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
DI
Diego
6 months ago
D just makes sense for protecting credentials.
NO
Noble
6 months ago
Hardcoding is a big no. A is risky!
NI
Nieves
7 months ago
B could work too, but not as secure as D.
MA
Malika
7 months ago
Agreed! Encrypted Key-Value Maps keep it safe.
WI
Willis
7 months ago
I think D is the best option. Security is key!
BL
Blossom
7 months ago
C seems risky, I’d go with D for sure.
AD
Adolph
7 months ago
Wait, can we really trust Key-Value Maps for sensitive info?
LI
Lili
8 months ago
Hardcoding credentials? No way, that’s a bad idea!
AJ
Aja
8 months ago
I think B is good too, but not as secure as D.
FE
Felicitas
8 months ago
Storing the credentials in configuration files? That's like leaving your house keys under the doormat. Encrypted key-value maps, people!
LI
Linn
8 months ago
Option D is the only way to keep those credentials safe and secure. Anything else is just asking for a security breach.
DE
Dexter
9 months ago
Storing the credentials in configuration files? That's just asking for trouble. Encrypted key-value maps all the way!
PE
Pete
9 months ago
Hardcoding the credentials in the code? That's a big no-no! Option B or D is the way to go.
YE
Yen
9 months ago
Option D is the way to go. Storing the credentials in encrypted key-value maps is the most secure approach.
HU
Hui
9 months ago
I’m leaning towards D too, but I wonder if there are any performance implications with accessing encrypted maps at runtime.
TA
Tanesha
9 months ago
I think we practiced a similar question where storing in configuration files was mentioned, but I can't recall if that was considered secure enough.
MA
Marshall
9 months ago
I feel like storing them in encrypted Key-Value Maps makes the most sense, but I’m not entirely sure if D is the only secure option.
MA
Martina
10 months ago
I remember we discussed the importance of not hardcoding credentials, so I think A is definitely out.
PA
Paulina
10 months ago
I'm a bit confused by this question. I'll need to review the material again to make sure I understand the best way to store the credentials securely.
ZI
Zita
10 months ago
D is definitely the best option for security.
SA
Sage
10 months ago
I'm leaning towards option B. Storing the credentials in key-value maps and accessing them at runtime could be a good way to keep them secure.
XU
Xuan
10 months ago
Option C looks good to me. Storing the credentials in configuration files and accessing them at runtime seems like a straightforward solution.
EL
Elenora
11 months ago
Hardcoded credentials? What is this, the 90s? Option D is the only way to go, unless you want your API to be hacked.
AL
Almeta
11 months ago
C is better than A, but still not ideal.
RO
Royal
11 months ago
Hmm, I'm not sure about this one. I'll need to think it through a bit more to decide which option is the best.
HO
Hollis
11 months ago
I think I'll go with option D. Storing the credentials in encrypted key-value maps seems like the most secure approach.
VI
Vivan
5 months ago
Absolutely, keeping it encrypted adds an extra layer of security.
TE
Teresita
6 months ago
Configuration files can be risky too. D is the way to go!
DI
Diane
6 months ago
Yeah, hardcoding is just asking for trouble.
SH
Sharika
6 months ago
Encrypted key-value maps are a solid way to protect sensitive info.
KI
Kirk
6 months ago
I agree, option D is definitely the safest choice.