Google Exam Cloud Digital Leader Topic 8 Question 34 Discussion

Actual exam question for Google's Cloud Digital Leader exam

Question #: 34
Topic #: 8

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?

AShare the information in a Github repository and grant access to the repo in IAM as required.

BStore the information in Secret Manager and give IAM read permissions as re-quired.

CStore the information in Kubernetes Secrets and only grant read permissions to users as required.

DEncrypt the information and store it in Cloud Storage for centralized access. Give the decrypt key only to the users who need to access it.

Show Suggested 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:

Submit Cancel

Shawn

2 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

Shayne

A) Share the information in a Github repository and grant access to the repo in IAM as required.

upvoted 0 times

...

Peggie

2 days 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

4 days 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

1 months ago

B) Store the information in Secret Manager and give IAM read permissions as required.

upvoted 0 times

...

Sherill

2 months ago

A) Share the information in a Github repository and grant access to the repo in IAM as required.

upvoted 0 times

...

Lai

2 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

2 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

2 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

26 days ago

B) Store the information in Secret Manager and give IAM read permissions as required.

upvoted 0 times

...

Chandra

2 months ago

B) Store the information in Secret Manager and give IAM read permissions as required.

upvoted 0 times

...

Isabella

2 months ago

B) Store the information in Secret Manager and give IAM read permissions as required.

upvoted 0 times

...

Andree

2 months ago

A) Share the information in a Github repository and grant access to the repo in IAM as required.

upvoted 0 times

...

Nell

2 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

3 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

3 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

...