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 healthcare enterprise configures an Assured Workloads folder using the US Data Boundary for Healthcare and Life Sciences control package to maintain HIPAA compliance. An engineering team requires a Google Cloud service that is covered under Google Cloud's HIPAA Business Associate Agreement (BAA) and supports US data residency and CMEK, but is not included in the control package's default service list.
A cloud security engineer updates the gcp.restrictServiceUsage organization policy constraint on the folder to allow the service. Following this change, Assured Workloads continuous monitoring flags compliance violations on the modified resources.
What action should the security engineer take to resolve the continuous monitoring alerts while maintaining a compliant posture?
roles/assuredworkloads.monitoringServiceAgent role to the engineering team's user identities.The roles/assuredworkloads.monitoringServiceAgent role is a dedicated Google Cloud service agent role designed exclusively for internal Google service accounts to create Cloud Asset Inventory feeds and monitor Assured Workloads resources.
cloudasset.feeds.create and cloudasset.assets.exportResource) meant only for automated platform services.roles/assuredworkloads.admin to view and manage violations.Google Cloud internal automation needed authorization to create Cloud Asset Inventory notification feeds for continuous compliance tracking.
gcp.restrictServiceUsage organization policy constraint entirely from the Assured Workloads folder.Removing the gcp.restrictServiceUsage constraint eliminates all organizational restrictions on service enablement, allowing developers to provision any arbitrary Google Cloud service within the folder.
gcp.restrictServiceUsage constraint is a fundamental preventative control deployed by Assured Workloads to enforce baseline regulatory guardrails.The workload was running in a non-regulated development environment with no compliance or data residency obligations.
Assured Workloads continuous monitoring actively audits resources against the baseline requirements of the assigned compliance regime (such as HIPAA/HITRUST). When an administrator expands service availability by customizing the gcp.restrictServiceUsage organization policy constraint, Assured Workloads detects deviation from its preconfigured baseline and flags active compliance violations. Granting an exception in the Assured Workloads console acknowledges that the deviation was intentional, verified, and accepted by security administrators.
This approach directly satisfies the operational requirement to allow HIPAA-compliant services outside the default baseline while preserving active continuous monitoring and generating a documented compliance record.
Access Transparency generates near-real-time audit logs whenever Google personnel access customer content during support or maintenance activities. Access Approval requires explicit customer administrative sign-off before Google personnel can access customer resources.
gcp.restrictServiceUsage policy modifications.An organization intended to opt out of manual approval workflows for emergency Google Cloud technical support interventions in a non-regulated sandbox environment.
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