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 enforces strict Infrastructure-as-Code (IaC) baselines across its entire Google Cloud organization. To minimize the window of exposure caused by out-of-band modifications, the security engineering team must design a continuous drift detection and automated remediation pipeline.
The solution must satisfy the following architectural requirements:
Which architecture should the security team deploy?
This approach creates aggregated Cloud Logging sinks at the organization level filtered for Admin Activity audit logs, configured to forward log entries directly to HTTP-triggered Cloud Functions endpoints using Webhook destinations.
The goal was to export raw audit records to a SIEM via a Pub/Sub topic rather than orchestrating comprehensive posture and asset drift remediation.
This architecture combines Security Command Center (SCC) Continuous Exports, Cloud Asset Inventory (CAI) real-time feeds, Cloud Pub/Sub, and Cloud Functions to provide an enterprise-grade, event-driven drift detection and remediation pipeline across a Google Cloud organization.
Leveraging native Pub/Sub streaming with Cloud Functions creates an asynchronous, event-driven security workflow that operates in sub-second response times without the compute costs, latency, or API quota consumption of continuous batch scanning.
Compliance Manager in Security Command Center evaluates deployed resources against compliance frameworks (such as CIS Benchmarks, NIST, and ISO) and provides visibility into compliance posture and control coverage.
The security team only needed to map Security Command Center findings to industry regulatory compliance benchmarks and audit control mappings.
This approach relies on Cloud Composer (managed Apache Airflow) to run periodic, scheduled batch DAGs that execute terraform plan commands against state files, log discrepancies to BigQuery, and orchestrate reconciliations via Cloud Workflows.
terraform plan across hundreds of projects consumes heavy compute, exhausts Cloud Resource Manager and service API rate quotas, and introduces high operational overhead.The organization required scheduled, batch-based state synchronization and comprehensive historical drift reporting where sub-minute response times were not required.
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