Your team needs to prevent users from creating projects in the organization. Only the DevOps team should be allowed to create projects on behalf of the requester. Which two tasks should your team perform to handle this request? (Choose two.)
A.
Remove all users from the Project Creator role at the organizational level.
B.
Create an Organization Policy constraint, and apply it at the organizational level.
C.
Grant the Project Editor role at the organizational level to a designated group of users.
D.
Add a designated group of users to the Project Creator role at the organizational level.
E.
Grant the billing account creator role to the designated DevOps team.
E. I think that the billing account creator role is needed in this case.
https://cloud.google.com/resource-manager/docs/default-access-control#removing-default-roles
"After you designate your own Billing Account Creator and Project Creator roles, you can remove these roles from the organization resource to restrict those permissions to specifically designated users. "
"A,D" seems most accurate.
The following page talks about how Project Creator role is granted to all users by default, which is why "A" is necessary. And then there's a section about granting Project Creator to specific users which is where "D" comes in.
https://cloud.google.com/resource-manager/docs/default-access-control#removing-default-roles
AD is perfect.
A. Remove all users from the Project Creator role at the organizational level.
D. Add a designated group of users to the Project Creator role at the organizational level.
A. Remove all users from the Project Creator role at the organizational level.
D. Add a designated group of users to the Project Creator role at the organizational level.
https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints
https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints
I see no way to restrict project creation with an organizational policy. If that would have been possible I would have voted for it as restrictions can be overriden in GCP.
Seems to be AC
When an organization resource is created, all users in your domain are granted the Billing Account Creator and Project Creator roles by default.
As per the link https://cloud.google.com/resource-manager/docs/default-access-control#removing-default-roles
Hence A is definitely the answer.
Now to add the project creator we need to add the designated group to the project creator role specifically.
AD is the answer. There's nothing related to project creation in organization policy constraints.
upvoted 4 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mlyu
Highly Voted 4 years, 2 months ago[Removed]
Highly Voted 3 years, 8 months agotaka5094
Most Recent 2 months, 3 weeks ago[Removed]
1 year, 4 months agoAzureDP900
2 years agoAwesomeGCP
2 years, 1 month agoAzureDP900
2 years agoJeanphi72
2 years, 3 months agopiyush_1982
2 years, 4 months agoabsipat
2 years, 5 months agosyllox
3 years, 6 months agosyllox
3 years, 6 months agoDebasishLowes
3 years, 9 months agoAniyadu
3 years, 10 months ago[Removed]
4 years agogenesis3k
4 years agosyllox
3 years, 6 months agoCHECK666
4 years, 1 month ago