New Year Sale 2026! 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 Digital Leader Exam - Topic 8 Question 34 Discussion

Actual exam question for Google's Cloud Digital Leader exam
Question #: 34
Topic #: 8
[All Cloud Digital Leader Questions]

Your Google Cloud Platform [GCP] admin has to manage a bunch of API keys for external services that are accessed by different applications, which are used by a few teams. What is the best way to manage them?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Fletcher at Feb 04, 2023, 09:37 AM

Limited Time Offer

25%

Off

Get Premium Cloud Digital Leader Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Margot
4 months ago
I’m surprised people still consider A; it’s not safe at all!
upvoted 0 times
...
Rodolfo
4 months ago
D is a solid choice, but managing keys can get tricky.
upvoted 0 times
...
Sharika
4 months ago
Wait, why would anyone use A? That sounds risky!
upvoted 0 times
...
Kanisha
4 months ago
I think C could work too, but it's not as secure as B.
upvoted 0 times
...
Denny
4 months ago
B is definitely the best option for security.
upvoted 0 times
...
Louisa
5 months ago
Encrypting and storing in Cloud Storage sounds secure, but I wonder if it complicates access management too much for the teams involved.
upvoted 0 times
...
Serita
5 months ago
I’m a bit confused about Kubernetes Secrets versus Secret Manager. I feel like both could work, but I can't recall the specific advantages of one over the other.
upvoted 0 times
...
Lindsay
5 months ago
I think Secret Manager is the best option here. We practiced a similar question in class where it was emphasized for managing sensitive data.
upvoted 0 times
...
Billye
5 months ago
I remember we discussed the importance of keeping API keys secure, but I'm not sure if storing them in GitHub is a good idea.
upvoted 0 times
...
Mitzie
5 months ago
Validating the customer's inventory seems like the most important step in the Qualification phase, so I'll choose option A.
upvoted 0 times
...
Merilyn
5 months ago
This seems like a tricky one. I'll need to think through the expected behavior carefully.
upvoted 0 times
...
Franchesca
5 months ago
I'm a bit confused by this question. The options seem to cover different aspects of the discovery process, but I'm not sure which one is the most accurate description. I'll need to review my notes on Webex Video Mesh to make sure I understand the process before answering this.
upvoted 0 times
...
Remedios
5 months ago
Hmm, I'm a little unsure about this one. I know PBMs are involved in managing prescription drug costs, but I'm not sure about the other responsibilities. I'll have to think this through carefully.
upvoted 0 times
...
Shawn
10 months ago
Haha, storing API keys in a Github repo? That's like leaving your house keys under the doormat. Secret Manager is the clear winner here.
upvoted 0 times
Malinda
8 months ago
D) Encrypt the information and store it in Cloud Storage for centralized access. Give the decrypt key only to the users who need to access it.
upvoted 0 times
...
Freeman
8 months ago
Haha, storing API keys in a Github repo? That's like leaving your house keys under the doormat. Secret Manager is the clear winner here.
upvoted 0 times
...
Telma
8 months ago
B) Store the information in Secret Manager and give IAM read permissions as required.
upvoted 0 times
...
Shayne
8 months ago
A) Share the information in a Github repository and grant access to the repo in IAM as required.
upvoted 0 times
...
Peggie
8 months ago
D) Encrypt the information and store it in Cloud Storage for centralized access. Give the decrypt key only to the users who need to access it.
upvoted 0 times
...
Jeannine
8 months ago
Haha, storing API keys in a Github repo? That's like leaving your house keys under the doormat. Secret Manager is the clear winner here.
upvoted 0 times
...
Tamar
10 months ago
B) Store the information in Secret Manager and give IAM read permissions as required.
upvoted 0 times
...
Sherill
10 months ago
A) Share the information in a Github repository and grant access to the repo in IAM as required.
upvoted 0 times
...
...
Lai
10 months ago
Encrypting and storing in Cloud Storage? Sounds like a lot of work. I'll stick with Secret Manager, it's the easiest solution.
upvoted 0 times
...
Armando
10 months ago
I prefer option D. Encrypting the information and storing it in Cloud Storage adds an extra layer of security, and only giving the decrypt key to authorized users minimizes the risk of unauthorized access.
upvoted 0 times
...
Cathrine
11 months ago
Kubernetes Secrets? Ugh, I'd rather not manage all that YAML just for some API keys. Secret Manager seems like the way to go.
upvoted 0 times
Bethanie
9 months ago
B) Store the information in Secret Manager and give IAM read permissions as required.
upvoted 0 times
...
Chandra
10 months ago
B) Store the information in Secret Manager and give IAM read permissions as required.
upvoted 0 times
...
Isabella
10 months ago
B) Store the information in Secret Manager and give IAM read permissions as required.
upvoted 0 times
...
Andree
10 months ago
A) Share the information in a Github repository and grant access to the repo in IAM as required.
upvoted 0 times
...
...
Nell
11 months ago
Storing API keys in a Github repo? Nope, too risky! Let's go with Secret Manager, it's the most secure option.
upvoted 0 times
...
Fannie
11 months ago
I agree with Blondell. Storing the information in Secret Manager with IAM read permissions ensures that only authorized users can access the API keys.
upvoted 0 times
...
Blondell
11 months ago
I think option B is the best way to manage API keys. Secret Manager provides a secure and centralized way to store sensitive information.
upvoted 0 times
...

Save Cancel