CLOUD-DIGITAL-LEADER practice question 6 of 35

Your company security team manages access control to production systems using an LDAP directory group. How is this access control managed in the Google Cloud production project?

Full set: 411 questions
Answer options
A: Assign the proper role to the Service Account in the project's IAM Policy
B: Grant each user the roles/iam.serviceAccountUser role on a service account that exists in the Google Group.
C: Assign the proper role to the Google Group in the project's IAM Policy. Correct answer
D: Create the project in a folder with the same name as the LDAP directory group.
Correct Answer:
C. Assign the proper role to the Google Group in the project's IAM Policy.
Explanation

Google Cloud IAM lets you grant permissions to a Google Group exactly as you would to an individual principal. Most enterprises mirror their on-premises LDAP security groups into Google Groups by means of Cloud Directory Sync. Once the Google Group that represents the LDAP directory group exists, you place that group in the production project’s IAM policy and attach the appropriate predefined or custom role. This keeps membership management in LDAP while centralising permission assignment in a single IAM binding—no per-user or service-account changes are required.

Why Incorrect

A. Service accounts are for workloads, not human users; giving the role to a service account bypasses the LDAP group entirely.
B. roles/iam.serviceAccountUser only lets users impersonate a service account; it does not grant the needed production-system permissions.
D. Folder names do not confer permissions; IAM bindings, not resource naming, control access.

References

1. Google Cloud IAM documentation – “Grant access using Google Groups” (IAM overview)

https://cloud.google.com/iam/docs/overview#groups, para. 2–3.

2. Google Cloud Directory Sync Admin Guide – “Synchronizing LDAP groups to Google Cloud” (Section: Syncing groups), p. 13.

3. Google Cloud IAM Best Practices – “Use groups to manage access” (Best practices doc), bullet 3.

4. Google Cloud Resource Manager – “Folders do not provide implicit permissions” (Resource Manager docs, Concepts, para. 4).

Scroll to Top