Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A security engineer is evaluating IAM Role Recommendations in Google Cloud to transition an automated data processing service account away from the overly broad roles/editor basic role. While analyzing the recommendation in the Google Cloud console, the engineer notes the following details:
roles/editor with a narrower predefined role.What should the security engineer consider before applying this role recommendation to ensure production operations are not disrupted?
This option assumes that IAM Recommender performs comprehensive cross-engine authorization evaluation across IAM, storage ACLs, and Kubernetes RBAC.
The workload operated exclusively against native Cloud IAM resources and did not use GKE RBAC or legacy Cloud Storage ACLs.
roles/iam.roleAdmin) to allow it to self-apply the recommended custom role at runtime.The roles/iam.roleAdmin role grants administrative permissions (iam.roles.create, iam.roles.update, iam.roles.delete) to create and manage custom IAM roles within a project or organization.
The administrator executing the change needed the required IAM privileges to automatically generate a recommended custom role in the project.
In the Google Cloud console IAM recommendation impact viewer, permissions highlighted in blue with a machine learning icon represent permissions that are included in the recommended role because Recommender's ML models predict the principal will likely need them in the future based on peer usage patterns.
google.iam.policy.LateralMovementInsight) that identify service account impersonation chains across projects, not as blue ML-highlighted permission deltas.The console specifically flagged a Lateral Movement Insight showing cross-project service account impersonation paths.
IAM Recommender is a Policy Intelligence tool that compares granted permissions against exercised permissions over an observation period (by default, 90 days). It provides role recommendations and policy insights (google.iam.policy.Insight) to help security teams safely transition principals from overly permissive roles (such as basic roles like roles/editor or roles/owner) to tightly scoped predefined or custom roles.
When analyzing the impact of a role replacement in the Google Cloud console:
roles/editor will not break external authorizations.This approach ensures that all dependencies—both within IAM and in external systems like Cloud Storage ACLs and GKE RBAC—are fully validated before applying the recommendation.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated