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 has activated Security Command Center (SCC) at the organization level across their Google Cloud environment. A security engineer needs to configure granular Identity and Access Management (IAM) permissions to fulfill two specific operational requirements:
Folder-BU1), without viewing attack paths or resources outside that folder.Which combination of IAM role bindings should the security engineer implement?
roles/securitycentermanagement.admin to the central SecOps audit team at the organization level, and grant roles/securitycenter.settingsViewer to the divisional compliance team at the Folder-BU1 level.This option grants the Security Center Management Admin (roles/securitycentermanagement.admin) role to the central team and the Security Center Settings Viewer (roles/securitycenter.settingsViewer) role to the compliance team.
roles/securitycentermanagement.admin grants full read/write management over Security Center services and custom modules (such as Event Threat Detection and Security Health Analytics custom modules). It does not provide the unified read-only dashboard view of attack paths, findings, and assets required by the SecOps audit team.roles/securitycenter.settingsViewer grants read-only access to SCC service settings and module configurations (such as export filters and detection settings), but it does not grant access to view actual cloud assets or security finding instances.securitycentermanagement.admin is meant for engineers managing custom detection modules, not security auditors.securitycenter.settingsViewer exposes service configuration metadata rather than workload vulnerability and asset inventory data.The central team needed to author custom detection modules via the Security Center Management API, and the divisional team needed to audit SCC module configuration parameters rather than workload findings.
roles/securitycenter.admin to the central SecOps audit team at the organization level, and grant roles/securitycenter.adminViewer to the divisional compliance team at the Folder-BU1 level.This option assigns Security Center Admin (roles/securitycenter.admin) to the SecOps team at the organization level and assigns Security Center Admin Viewer (roles/securitycenter.adminViewer) to the compliance team at the folder level.
roles/securitycenter.admin is a highly privileged administrative role that provides full read and write access, including the ability to enable/disable security services, edit notification configurations, create mute rules, and update organization settings. Requirement 1 explicitly states the SecOps audit team must have read-only visibility without configuration update permissions.roles/securitycenter.adminViewer includes broad viewing privileges across attack paths and admin configurations and is designed for organization-level viewing rather than targeted folder-level asset/finding inspection. To restrict visibility to individual folders or projects, Google Cloud recommends using granular viewer roles (roles/securitycenter.assetsViewer and roles/securitycenter.findingsViewer).roles/securitycenter.admin grants destructive and muting capabilities across all security services.The central SecOps team required full administrative control over all SCC settings, services, and modules, and the divisional team required access to organization-level attack path modeling.
roles/securitycenter.adminViewer to the central SecOps audit team at the organization level, and grant roles/securitycenter.assetsViewer and roles/securitycenter.findingsViewer to the divisional compliance team at the Folder-BU1 level.Google Cloud Security Command Center (SCC) uses specialized Identity and Access Management (IAM) predefined roles that align with the resource hierarchy (Organization, Folder, and Project) to enforce least-privilege visibility and administration.
roles/securitycenter.adminViewer) role at the organization level provides comprehensive, read-only permissions across the entire organization. It allows the team to inspect all discovered assets, security findings, and attack exposure paths in the Security Command Center console without granting permissions to change configurations, mute findings, or modify detection services.roles/securitycenter.assetsViewer) and Security Center Findings Viewer (roles/securitycenter.findingsViewer) roles specifically at the Folder-BU1 level scopes asset and finding visibility strictly to resources nested under that specific folder. It prevents the divisional compliance team from seeing findings, assets, or attack paths elsewhere in the organization hierarchy.securitycenter.*.update or securitycenter.*.create), preventing accidental or malicious modification of security baselines.This configuration cleanly separates organization-wide administrative auditing from departmental finding reviews, strictly enforcing least privilege through native Google Cloud Resource Manager hierarchy boundaries.
roles/securitycenter.findingsViewer and roles/securitycenter.assetsViewer to the central SecOps audit team at the organization level, and grant roles/securitycenter.findingsEditor to the divisional compliance team at the Folder-BU1 level.This option pairs roles/securitycenter.findingsViewer and roles/securitycenter.assetsViewer at the organization level for the audit team while assigning roles/securitycenter.findingsEditor to the compliance team on Folder-BU1.
roles/securitycenter.findingsViewer and roles/securitycenter.assetsViewer only covers assets and findings; it does not grant the ability to view attack paths and simulation data across SCC. The SecOps audit team specifically requires attack path visibility, which requires roles/securitycenter.adminViewer.roles/securitycenter.findingsEditor allows users to edit finding states, add security marks, and mute findings. Requirement 2 mandates read-only access for the divisional compliance team to review findings and assets.roles/securitycenter.findingsEditor exceeds least privilege by allowing modification and muting of active vulnerability findings.The SecOps team had no need to view attack exposure simulations, and the divisional compliance team was responsible for triaging, editing, and muting findings directly within their folder.
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