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 multinational financial services institution is migrating a mission-critical payment processing system to Google Cloud. The compliance and security teams mandate a comprehensive, end-to-end data protection strategy that enforces strict data confidentiality across all stages of the data lifecycle:
Which architecture meets all of these end-to-end data protection requirements?
This architecture establishes network-level boundaries using VPC Service Controls service perimeters, enables Private Google Access for private API routing, and applies Cloud Armor rules for web application firewall (WAF) filtering on edge load balancers.
The primary objective was establishing a network boundary to prevent data exfiltration from Google-managed APIs to untrusted public endpoints.
This configuration deploys Shielded VM instances with Secure Boot and virtual Trusted Platform Module (vTPM) integrity monitoring, utilizes IPSec tunneling for internal communications, and uses default Google-owned and Google-managed encryption keys (GMEK) for data at rest.
The workload only required verification of operating system baseline integrity (prevention of kernel tampering) and standard baseline cloud storage encryption, rather than runtime memory encryption and customer-managed key governance.
This architecture combines Confidential Computing, Customer-Managed Encryption Keys (CMEK) with Cloud HSM, and managed SSL/TLS Policies on Cloud Load Balancing to achieve comprehensive cryptographic protection across data at rest, data in transit, and data in use.
This solution directly addresses every stage of the data lifecycle without operational blind spots, ensuring data confidentiality is maintained from network transit to persistent storage and active memory execution.
This design uses Sensitive Data Protection (Cloud DLP) to discover, tokenize, and redact sensitive attributes prior to storage, while using Binary Authorization to ensure only cryptographically signed container images are deployed onto standard Google Kubernetes Engine (GKE) worker nodes.
The primary goal was application-level data de-identification, PII masking in analytics pipelines, and container supply chain security.
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