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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Cloud - Apigee Certified API Engineer Exam - Topic 3 Question 12 Discussion

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?
D) Stored in encrypted Key-Value Maps and access at run time.
A) Hardcoded in Assign Message policy
B) Stored in Key-Value Maps and accessed at run time.
C) Stored in configuration files and make use at run time.

Google Cloud - Apigee Certified API Engineer Exam - Topic 3 Question 12 Discussion

Actual exam question for Google's Google Cloud - Apigee Certified API Engineer exam
Question #: 12
Topic #: 3
[All Google Cloud - Apigee Certified API Engineer Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Geoffrey at Nov 20, 2025, 02:43 AM

Limited Time Offer

25%

Off

Get Premium Google Cloud - Apigee Certified API Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Diego
5 months ago
D just makes sense for protecting credentials.
upvoted 0 times
...
Noble
5 months ago
Hardcoding is a big no. A is risky!
upvoted 0 times
...
Nieves
5 months ago
B could work too, but not as secure as D.
upvoted 0 times
...
Malika
5 months ago
Agreed! Encrypted Key-Value Maps keep it safe.
upvoted 0 times
...
Willis
5 months ago
I think D is the best option. Security is key!
upvoted 0 times
...
Blossom
6 months ago
C seems risky, I’d go with D for sure.
upvoted 0 times
...
Adolph
6 months ago
Wait, can we really trust Key-Value Maps for sensitive info?
upvoted 0 times
...
Lili
6 months ago
Hardcoding credentials? No way, that’s a bad idea!
upvoted 0 times
...
Aja
7 months ago
I think B is good too, but not as secure as D.
upvoted 0 times
...
Felicitas
7 months ago
Storing the credentials in configuration files? That's like leaving your house keys under the doormat. Encrypted key-value maps, people!
upvoted 0 times
...
Linn
7 months ago
Option D is the only way to keep those credentials safe and secure. Anything else is just asking for a security breach.
upvoted 0 times
...
Dexter
7 months ago
Storing the credentials in configuration files? That's just asking for trouble. Encrypted key-value maps all the way!
upvoted 0 times
...
Pete
7 months ago
Hardcoding the credentials in the code? That's a big no-no! Option B or D is the way to go.
upvoted 0 times
...
Yen
7 months ago
Option D is the way to go. Storing the credentials in encrypted key-value maps is the most secure approach.
upvoted 0 times
...
Hui
8 months ago
I’m leaning towards D too, but I wonder if there are any performance implications with accessing encrypted maps at runtime.
upvoted 0 times
...
Tanesha
8 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.
upvoted 0 times
...
Marshall
8 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.
upvoted 0 times
...
Martina
8 months ago
I remember we discussed the importance of not hardcoding credentials, so I think A is definitely out.
upvoted 0 times
...
Paulina
8 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.
upvoted 0 times
...
Zita
8 months ago
D is definitely the best option for security.
upvoted 0 times
...
Sage
9 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.
upvoted 0 times
...
Xuan
9 months ago
Option C looks good to me. Storing the credentials in configuration files and accessing them at runtime seems like a straightforward solution.
upvoted 0 times
...
Elenora
9 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.
upvoted 0 times
...
Almeta
9 months ago
C is better than A, but still not ideal.
upvoted 0 times
...
Royal
9 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.
upvoted 0 times
...
Hollis
10 months ago
I think I'll go with option D. Storing the credentials in encrypted key-value maps seems like the most secure approach.
upvoted 0 times
Vivan
4 months ago
Absolutely, keeping it encrypted adds an extra layer of security.
upvoted 0 times
...
Teresita
4 months ago
Configuration files can be risky too. D is the way to go!
upvoted 0 times
...
Diane
4 months ago
Yeah, hardcoding is just asking for trouble.
upvoted 0 times
...
Sharika
4 months ago
Encrypted key-value maps are a solid way to protect sensitive info.
upvoted 0 times
...
Kirk
5 months ago
I agree, option D is definitely the safest choice.
upvoted 0 times
...
...

Save Cancel