Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is reviewing the security posture of an analytics environment in Google Cloud. Several data engineers currently have the primitive roles/editor role granted at the project level, which grants overly broad permissions across Google Cloud services such as Cloud Bigtable and BigQuery.
You have the following operational and security requirements:
Which strategy should you implement?
IAM Recommender utilizes machine learning and historical audit logging to analyze permission usage patterns over a rolling 90-day window. It automatically identifies discrepancies between the permissions granted to a principal and the permissions actually exercised, generating actionable recommendations to replace overly permissive roles.
Predefined roles are curated and maintained directly by Google Cloud. They group permissions tailored to specific job functions (e.g., roles/bigtable.user or roles/bigquery.user) and are automatically updated by Google when new API methods and features are added to that service.
roles/editor primitive role and recommends tighter predefined roles matching the engineers' actual tasks.Primitive roles (roles/owner, roles/editor, roles/viewer) grant broad access across almost every resource in a project and violate the principle of least privilege. Replacing them with Google-managed predefined roles suggested by IAM Recommender gives precise access while ensuring zero maintenance overhead when APIs change.
Primitive roles (specifically roles/owner, roles/editor, and roles/viewer) are legacy Google Cloud roles that offer coarse-grained, blanket permissions across all services in a project. roles/viewer grants read access across nearly all project resources, while roles/owner grants full administrative control, including managing IAM policies and deleting resources.
roles/viewer still exposes sensitive metadata and data across all unrelated project resources, violating least privilege.roles/owner access introduces significant risk of accidental project deletion or unauthorized IAM manipulation.roles/owner allows altering IAM allow policies and billing attributes.The organization had a very small test project with non-sensitive data and no requirement for fine-grained access segregation.
Custom IAM roles allow administrators to create user-defined collections of specific permissions when no existing predefined role meets their exact security or governance criteria.
No combination of Google-managed predefined roles could satisfy a strict compliance rule that required isolating individual API methods.
Service agent roles (such as roles/datafusion.serviceAgent or roles/cloudfunctions.serviceAgent) are specialized IAM roles designed specifically for Google-managed internal service accounts (service agents) that allow Google Cloud services to run background processes and interact with other APIs on your behalf.
A built-in Google Cloud service needed automated cross-service communication to perform backend orchestration tasks.
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