Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Security Engineer Topic 2 Question 59 Discussion

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

You want data on Compute Engine disks to be encrypted at rest with keys managed by Cloud Key Management Service (KMS). Cloud Identity and Access Management (IAM) permissions to these keys must be managed in a grouped way because the permissions should be the same for all keys.

What should you do?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Marica
2 months ago
Forget the keys, let's just encrypt everything with duct tape. That's the real Cloud KMS.
upvoted 0 times
Meghan
5 days ago
B) Create a single KeyRing for all persistent disks and all Keys in this KeyRing. Manage the IAM permissions at the KeyRing level.
upvoted 0 times
...
Salina
12 days ago
A) Create a single KeyRing for all persistent disks and all Keys in this KeyRing. Manage the IAM permissions at the Key level.
upvoted 0 times
...
Boris
21 days ago
C) Create a KeyRing per persistent disk, with each KeyRing containing a single Key. Manage the IAM permissions at the Key level.
upvoted 0 times
...
Melinda
1 months ago
B) Create a single KeyRing for all persistent disks and all Keys in this KeyRing. Manage the IAM permissions at the KeyRing level.
upvoted 0 times
...
Rossana
1 months ago
A) Create a single KeyRing for all persistent disks and all Keys in this KeyRing. Manage the IAM permissions at the Key level.
upvoted 0 times
...
...
Carli
2 months ago
Ah, the joys of cloud infrastructure! I think I'll go with B - less keys, less problems, am I right?
upvoted 0 times
...
Lottie
2 months ago
This question is like a treasure hunt, but the treasure is just more bureaucracy. I'll go with B, just to keep things from getting too messy.
upvoted 0 times
Dacia
27 days ago
Yeah, B is the way to go to avoid unnecessary complexity.
upvoted 0 times
...
Glendora
1 months ago
I agree, B seems like the simplest option to manage IAM permissions.
upvoted 0 times
...
...
Sanjuana
2 months ago
Hmm, I'm torn between B and D. But I guess B makes more sense since it's less administrative overhead.
upvoted 0 times
...
Albert
2 months ago
But wouldn't managing permissions at the Key level provide more granular control over access to the keys?
upvoted 0 times
...
Sylvie
2 months ago
I disagree, I believe creating a KeyRing per persistent disk and managing IAM permissions at the KeyRing level would be more secure.
upvoted 0 times
...
Mitzie
2 months ago
Option B is the way to go! Manage the IAM permissions at the KeyRing level to keep things simple and streamlined.
upvoted 0 times
Geoffrey
27 days ago
Definitely. It's all about efficiency and security when it comes to managing access to sensitive data.
upvoted 0 times
...
Lorrine
1 months ago
I agree. It's important to keep things organized when dealing with encryption keys.
upvoted 0 times
...
Devora
1 months ago
That makes sense. It would be easier to manage permissions that way.
upvoted 0 times
...
Gilberto
2 months ago
Option B is the way to go! Manage the IAM permissions at the KeyRing level to keep things simple and streamlined.
upvoted 0 times
...
...
Albert
3 months ago
I think we should create a single KeyRing for all persistent disks and manage IAM permissions at the Key level.
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