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.
An enterprise organization manages microservices across hundreds of projects grouped under environment-specific folders in Google Cloud. The security team needs to configure IAM access according to the principle of least privilege for two distinct teams:
Which IAM role and resource hierarchy binding strategy should the security engineer implement?
roles/cloudhub.operator) at the organization level, and grant development team Google Groups the App Management Viewer role (roles/apphub.appManagementViewer) on the parent folder.This strategy grants organization-wide operator permissions to SREs and binds folder-level application viewing permissions to developers on the parent folder.
roles/cloudhub.operator at the organization root cascades down the entire resource hierarchy, granting SREs operator permissions across every current and future project regardless of whether it is an app-enabled environment.roles/apphub.appManagementViewer at the folder level grants developers read visibility into all sibling applications and services residing in that folder, violating the requirement to restrict them strictly to their assigned projects.SREs required universal operator permissions across all enterprise projects and developers were responsible for managing the entire folder's application fleet.
roles/apphub.appManagementViewer) at the organization level, and grant development team Google Groups the Cloud Hub Operator role (roles/cloudhub.operator) on the parent folder.This option applies the application viewer role at the root organization node and assigns project operator roles at the shared parent folder level.
roles/cloudhub.operator at the folder level causes all members of the developer groups to inherit operator permissions across every project in that folder due to IAM policy inheritance.All development teams needed full operational visibility across every project in the environment folder and SREs managed organization-wide infrastructure portfolios.
roles/cloudhub.operator) on the app-enabled folder, and grant individual developer accounts the App Management Viewer role (roles/apphub.appManagementViewer) on their respective projects.This configuration attempts to grant the project-level operator role at the folder level to SREs and binds the folder-oriented application management viewer role to individual developer accounts on project resources.
roles/cloudhub.operator role is designed specifically for project-level operators and developers managing particular projects, not for folder-level application health aggregation.roles/apphub.appManagementViewer role requires binding to an app-enabled folder to view holistic application health, rather than being bound to individual project resources.Individual developers were responsible for cross-project application topology definitions and SREs only acted as project-level operators, which contradicts standard cloud governance practices.
roles/apphub.appManagementViewer) on the app-enabled folder, and grant each development team Google Group the Cloud Hub Operator role (roles/cloudhub.operator) on their respective projects.This solution assigns predefined IAM roles to managed Google Groups at appropriate levels of the Google Cloud resource hierarchy, pairing the App Management Viewer (roles/apphub.appManagementViewer) role at the folder level with the Cloud Hub Operator (roles/cloudhub.operator) role at individual project levels.
roles/apphub.appManagementViewer on an app-enabled folder grants Site Reliability Engineers view permissions across all registered applications and components aggregated under that folder.roles/cloudhub.operator on specific target projects ensures developer access is confined strictly to the operational boundaries of their designated project workloads without exposing surrounding folder-level application architectures.Predefined Cloud Hub and App Hub roles are purpose-built for this exact architectural separation: roles/apphub.appManagementViewer provides application-level monitoring across folders, while roles/cloudhub.operator provides project-level metric and telemetry viewing.
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