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-DevOps-Engineer Topic 3 Question 63 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 63
Topic #: 3
[All Professional Cloud DevOps Engineer Questions]

Your company operates in a highly regulated domain. Your security team requires that only trusted container images can be deployed to Google Kubernetes Engine (GKE). You need to implement a solution that meets the requirements of the security team, while minimizing management overhead. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Hoa
4 months ago
But with Binary Authorization, we can ensure only trusted container images are deployed.
upvoted 0 times
...
Callie
4 months ago
I'm not sure. Option C with Kritis also seems like a valid solution to enforce security policies.
upvoted 0 times
...
Chau
4 months ago
I agree with Hoa. Option D with Binary Authorization seems like the way to go.
upvoted 0 times
...
Hoa
4 months ago
I think option D sounds like a good choice. It enforces security policies at deploy time.
upvoted 0 times
...
My
5 months ago
I see your point, Josephine, but Binary Authorization directly enforces the policies at deploy-time, which may be more effective.
upvoted 0 times
...
Josephine
5 months ago
I'm not sure, wouldn't configuring Kritis in our GKE clusters also help enforce deploy-time security policies?
upvoted 0 times
...
Bernadine
5 months ago
I agree with My, Binary Authorization seems like the best way to ensure only trusted container images are deployed.
upvoted 0 times
...
My
5 months ago
I think we should go with option D), configure Binary Authorization in our GKE clusters.
upvoted 0 times
...
Hershel
6 months ago
Option C with Kritis is also an interesting option. It lets us define custom security policies and apply them to our deployments. But it might be a bit more complex to set up and maintain.
upvoted 0 times
...
Otis
6 months ago
Yeah, Binary Authorization seems like the most straightforward solution. We don't have to worry about managing additional services or permissions. It just handles the policy enforcement for us.
upvoted 0 times
...
Franchesca
6 months ago
Haha, yeah, the less we have to manage, the better. I'm all about that low-maintenance approach. Binary Authorization is sounding better and better.
upvoted 0 times
...
Kimberely
6 months ago
True, Kritis could be a bit more hands-on. Plus, I'm a little worried about the management overhead with a custom validator in Option B. Gotta keep that overhead to a minimum, you know?
upvoted 0 times
Kenda
6 months ago
C) Configure Kritis to run in your GKE clusters to enforce deploy-time security policies.
upvoted 0 times
...
Timothy
6 months ago
D) Configure Binary Authorization in your GKE clusters to enforce deploy-time security policies
upvoted 0 times
...
Tiera
6 months ago
A) Grant the roles/artifactregistry. writer role to the Cloud Build service account. Confirm that no employee has Artifact Registry write permission.
upvoted 0 times
...
Dean
6 months ago
D) Configure Binary Authorization in your GKE clusters to enforce deploy-time security policies
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77