GCP Associate Cloud Engineer Practice Question 59: IAM Recommender Excess Permissions
Google Cloud Associate Cloud Engineer · Test 6 · question 9 of 10
A security review finds that several users and service accounts in a project hold broad predefined roles such as Editor, but nobody is sure which permissions each principal actually uses day to day. You want a way to identify, for every principal in the project, which of their granted permissions are unused so that you can right-size their roles without guessing or manually auditing each principal's activity logs.
What should you do?
Show answer and explanation
Answer:
IAM role recommendations, generated by the IAM recommender in Recommender (part of Policy Intelligence), compare each principal's granted permissions against the permissions it actually used over an observation period (up to 90 days). Where a principal is not using some or all of a role's permissions, the recommender suggests removing the role or replacing it with a narrower predefined role, custom role, or combination that still covers observed usage; it never suggests a change that grants more access than the principal already has. This gives per-principal, evidence-based right-sizing across the whole project without manual log analysis.
Option A is a manual, error-prone substitute for a feature Google already provides, and hand-built roles from a single log export can miss legitimate but infrequent activity. Option C only stops new Editor grants going forward; it does nothing to identify or remove the excess permissions already held by existing principals. Option D describes a deny policy built from guesswork about job duties rather than observed usage, and deny policies block access rather than reveal what permissions are actually unused.
Reference: Overview of role recommendations