Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Associate Cloud Engineer Topic 5 Question 94 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 94
Topic #: 5
[All Associate Cloud Engineer Questions]

During a recent audit of your existing Google Cloud resources, you discovered several users with email addresses outside of your Google Workspace domain.

You want to ensure that your resources are only shared with users whose email addresses match your domain. You need to remove any mismatched users, and you want to avoid having to audit your resources to identify mismatched users. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints This list constraint defines the set of domains that email addresses added to Essential Contacts can have. By default, email addresses with any domain can be added to Essential Contacts. The allowed/denied list must specify one or more domains of the form @example.com. If this constraint is active and configured with allowed values, only email addresses with a suffix matching one of the entries from the list of allowed domains can be added in Essential Contacts. This constraint has no effect on updating or removing existing contacts. constraints/essentialcontacts.allowedContactDomains


Contribute your Thoughts:

Becky
2 months ago
Haha, I bet one of those mismatched users is the CEO's nephew or something. Better tread carefully with D)!
upvoted 0 times
Sunshine
1 months ago
Haha, I bet one of those mismatched users is the CEO's nephew or something. Better tread carefully with D)!
upvoted 0 times
...
Marget
1 months ago
C) Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.
upvoted 0 times
...
Tonette
2 months ago
A) Create a Cloud Scheduler task to regularly scan your projects and delete mismatched users.
upvoted 0 times
...
...
Mireya
2 months ago
This is a classic case of 'work smarter, not harder.' C) is the winner here - set it and forget it!
upvoted 0 times
Francoise
1 months ago
Agreed, setting it and forgetting it is the way to go.
upvoted 0 times
...
Chauncey
1 months ago
Definitely! It will save us a lot of time and effort.
upvoted 0 times
...
Gail
2 months ago
That sounds like a great solution!
upvoted 0 times
...
Gregoria
2 months ago
C) Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.
upvoted 0 times
...
...
Colton
2 months ago
I'm not sure about option D. It seems like a lot of work to retroactively remove mismatched users. I think option C is the way to go.
upvoted 0 times
...
Felicidad
3 months ago
B) sounds like the best choice. Regularly scanning the resources and removing the bad users is the most thorough approach, even if it takes a bit more effort.
upvoted 0 times
...
Dorothy
3 months ago
D) is the way to go. Gotta make sure we get rid of those pesky mismatched users, but the retroactive part is key to clean things up properly.
upvoted 0 times
Margret
1 months ago
Agreed, D) is the best option to clean up the existing mismatched users and prevent future ones.
upvoted 0 times
...
Myrtie
1 months ago
D) Set an organizational policy constraint to limit identities by domain, and then retroactively remove the existing mismatched users.
upvoted 0 times
...
Malcolm
2 months ago
C) Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.
upvoted 0 times
...
...
Hassie
3 months ago
I agree with Lashawn. Setting an organizational policy constraint seems like the most efficient way to handle this issue.
upvoted 0 times
...
Corazon
3 months ago
C) seems like the most straightforward option to me. Why waste time scanning and deleting users manually when we can just set a policy to automatically handle it?
upvoted 0 times
Toshia
2 months ago
Let's set the policy and remove those mismatched users automatically.
upvoted 0 times
...
Nadine
2 months ago
I think we should go ahead and implement that option to ensure our resources are secure.
upvoted 0 times
...
Chaya
2 months ago
It would definitely save us time and effort in the long run.
upvoted 0 times
...
Sommer
2 months ago
I agree, setting an organizational policy constraint sounds like the most efficient solution.
upvoted 0 times
...
...
Lashawn
3 months ago
I think option C sounds like the best solution. It would automatically remove mismatched users based on domain.
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