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

Google Exam Professional Cloud Security Engineer Topic 1 Question 64 Discussion

Actual exam question for Google's Professional Cloud Security Engineer exam
Question #: 64
Topic #: 1
[All Professional Cloud Security Engineer Questions]

Your organization is using GitHub Actions as a continuous integration and delivery (Cl/CD) platform. You must enable access to Google Cloud resources from the Cl/CD pipelines in the most secure way.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Felicidad
17 days ago
Option C with a GKE cluster and Workload Identity is also a good choice. But if I had to pick one, I'd go with D. Gotta keep those cloud credentials secure, ya know?
upvoted 0 times
Yan
2 days ago
A) Create a service account key and add it to the GitHub pipeline configuration file.
upvoted 0 times
...
...
Pamella
19 days ago
Haha, storing a service account key in the repo? That's like leaving your house keys under the doormat. Option D is the clear winner here.
upvoted 0 times
...
Kirby
26 days ago
I agree, option D is the way to go. Workload identity federation is the recommended approach for this use case. Storing sensitive service account keys in the pipeline config or repository is a big no-no.
upvoted 0 times
...
Janey
27 days ago
Option D seems like the most secure way to enable access to Google Cloud resources from the CI/CD pipelines. Using workload identity federation to integrate GitHub as an identity provider is a best practice.
upvoted 0 times
...
Yong
2 months ago
I'm not sure, but configuring workload identity federation to use GitHub as an identity pool provider could also be a good option.
upvoted 0 times
...
Kirby
2 months ago
I agree with Reita, adding the service account key to the pipeline configuration file seems like the most secure option.
upvoted 0 times
...
Reita
2 months ago
I think we should create a service account key and add it to the GitHub pipeline configuration file.
upvoted 0 times
...

Save Cancel