MENU
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?
Suggested Answer: D
Get Premium Associate Cloud Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
37 comments · newest first
CA
Carol
11 months ago
I heard Cloud Scheduler can be a bit tricky to set up.
CE
Cecilia
11 months ago
Option D seems more thorough, though.
ER
Erasmo
11 months ago
Wait, can you really set a policy to auto-remove users? Sounds too good to be true.
AU
Audria
11 months ago
Definitely agree with that!
DI
Dierdre
12 months ago
I think option C is the best choice.
XO
Xochitl
12 months ago
I definitely remember that setting an organizational policy is a good way to prevent mismatched users, but I’m uncertain about the specifics of retroactive removal.
BE
Bettyann
1 year ago
I feel like using Cloud Scheduler to scan resources is a bit overkill for this situation. It seems like a more manual approach.
CH
Chara
1 year ago
I think we practiced a similar question where setting a policy was the best approach, but I can't recall if it was option C or D.
CR
Craig
1 year ago
I remember discussing how organizational policies can help enforce domain restrictions, but I'm not sure if they can retroactively remove users.
RA
Rashad
1 year ago
The organizational policy constraint seems like the way to go. That way, we can set it and forget it, and not have to worry about constantly monitoring and removing mismatched users.
JU
Juan
1 year ago
I'm a bit confused on the difference between the Cloud Scheduler task options. Do they have any significant differences, or are they essentially the same approach?
CL
Cletus
1 year ago
I'm leaning towards the organizational policy constraint option. That sounds like the most efficient way to handle this and prevent future issues.
SH
Sharika
1 year ago
Okay, let's see. I think the key here is finding a way to automatically remove any mismatched users without having to manually audit everything. That would be a huge time-saver.
DA
Danica
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about the best approach to ensure our resources are only accessible to the right users.
GL
Glenn
1 year ago
This seems like a straightforward question about boiler water condensate corrosion. I'll need to think through the major factors that can contribute to this issue.
BE
Becky
2 years ago
Haha, I bet one of those mismatched users is the CEO's nephew or something. Better tread carefully with D)!
SU
Sunshine
2 years ago
Haha, I bet one of those mismatched users is the CEO's nephew or something. Better tread carefully with D)!
MA
Marget
2 years ago
C) Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.
TO
Tonette
2 years ago
A) Create a Cloud Scheduler task to regularly scan your projects and delete mismatched users.
MI
Mireya
2 years ago
This is a classic case of 'work smarter, not harder.' C) is the winner here - set it and forget it!
FR
Francoise
2 years ago
Agreed, setting it and forgetting it is the way to go.
CH
Chauncey
2 years ago
Definitely! It will save us a lot of time and effort.
GA
Gail
2 years ago
That sounds like a great solution!
GR
Gregoria
2 years ago
C) Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.
CO
Colton
2 years 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.
FE
Felicidad
2 years 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.
DO
Dorothy
2 years 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.
MA
Margret
2 years ago
Agreed, D) is the best option to clean up the existing mismatched users and prevent future ones.
MY
Myrtie
2 years ago
D) Set an organizational policy constraint to limit identities by domain, and then retroactively remove the existing mismatched users.
MA
Malcolm
2 years ago
C) Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.
HA
Hassie
2 years ago
I agree with Lashawn. Setting an organizational policy constraint seems like the most efficient way to handle this issue.
CO
Corazon
2 years 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?
TO
Toshia
2 years ago
Let's set the policy and remove those mismatched users automatically.
NA
Nadine
2 years ago
I think we should go ahead and implement that option to ensure our resources are secure.
CH
Chaya
2 years ago
It would definitely save us time and effort in the long run.
SO
Sommer
2 years ago
I agree, setting an organizational policy constraint sounds like the most efficient solution.
LA
Lashawn
2 years ago
I think option C sounds like the best solution. It would automatically remove mismatched users based on domain.