Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An enterprise is adopting the Google Cloud Security Foundations blueprint to govern and secure its infrastructure across multiple environments. The DevOps and platform teams need to establish an automated, declarative GitOps workflow that continuously validates infrastructure definitions against compliance benchmarks, prevents configuration drift, and enforces security constraints before and during resource admission.
Which approach should the team implement to meet these governance and compliance requirements?
Config Sync and Policy Controller are core declarative governance tools in Google Cloud. Config Sync manages and continuously synchronizes infrastructure configurations from a centralized, version-controlled repository, while Policy Controller acts as an admission controller and compliance auditor that enforces programmable rules based on the Open Policy Agent (OPA) framework.
Combining Config Sync with Policy Controller provides shift-left policy enforcement, zero-touch production compliance, and automated remediation without introducing brittle scripts, persistent credentials, or manual review bottlenecks.
This approach uses Google Security Operations (SecOps) SOAR playbooks paired with domain-wide delegation to detect drift and trigger automated rollback actions after resources have already been modified.
The primary goal was automated Security Operations Center (SOC) incident response to remediate compromised user accounts or isolate compromised hosts based on live threat telemetry.
This method uses downloaded service account JSON keys stored on local developer workstations to run client-side validation scripts against Google Cloud APIs before pushing code.
iam.disableServiceAccountKeyCreation) because downloaded keys pose severe credential exfiltration risks.The organization had no central CI/CD or policy orchestration framework and was conducting temporary, read-only API audits from isolated test systems.
This approach relies on granting developers highly privileged emergency (breakglass) accounts with the roles/resourcemanager.organizationAdmin role to perform direct, manual troubleshooting and updates in production environments.
An emergency situation occurred where all automated pipelines failed, requiring designated incident responders to temporarily access the environment to restore critical systems.
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