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 financial services organization hosted on Google Cloud must comply with strict regulatory auditability and threat monitoring requirements across all existing and future projects in its resource hierarchy. The compliance and security teams mandate the following requirements:
DATA_READ, DATA_WRITE, and ADMIN_READ) across all services.Which architecture should the security engineer implement to satisfy these compliance and monitoring requirements?
This architecture focuses on microservice workload auditing via Cloud Service Mesh and ingesting raw event streams into Google Security Operations SIEM using Pub/Sub and CMEK-encrypted Cloud Storage.
The primary objective was to audit L7 HTTP/gRPC service-to-service transactions within a Kubernetes environment and ingest them into an external SIEM platform.
includeChildren=true targeting a dedicated Cloud Storage bucket; enforce a 7-year retention policy locked with Bucket Lock; and enable Security Command Center with Event Threat Detection.This architecture establishes a centralized, organization-wide logging, immutable retention, and automated threat detection framework using Google Cloud native compliance controls.
DATA_READ, DATA_WRITE, and ADMIN_READ log types across all services and child resources. Admin Activity logs are enabled by default.includeChildren=true intercepts and routes all audit log entries from all current and future folders and projects into a centralized compliance destination.Alternative approaches that rely on project-level log exports or standard IAM ACLs introduce operational overhead, allow accidental gaps in new projects, and fail to guarantee true immutability against privileged administrative overrides.
This approach relies on decentralized, project-by-project IAM audit log configurations combined with standard project-level sinks exporting to a BigQuery dataset with table partition expiration.
bigquery.admin or table editing roles.The requirement specifically called for performing ad-hoc SQL analytics on log data within an isolated single project without requiring WORM regulatory immutability.
logging.buckets.delete permission for all users and service accounts.This configuration sets folder-scoped audit logging and uses Cloud Logging log bucket retention coupled with IAM Deny policies to restrict bucket deletion.
resourcemanager.organizationAdmin), meaning they do not satisfy regulatory WORM compliance standards.The organization only required regional log residency within Cloud Logging buckets without strict WORM regulatory mandates or real-time threat intelligence detection.
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