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 organization is establishing baseline compute and workload security controls on Google Cloud to comply with strict regulatory mandates. The architecture includes workloads running on Compute Engine instances and Google Kubernetes Engine (GKE) clusters.
The regulatory framework requires the following technical safeguards:
Which combination of Google Cloud security controls and configurations should the organization implement to satisfy these compliance requirements?
This option combines Customer-Managed Encryption Keys (CMEK) via Cloud Key Management Service (Cloud KMS) for persistent storage encryption, VPC Service Controls for API data-exfiltration prevention, GKE Sandbox (gVisor) for kernel-level container sandboxing, and Google Cloud Armor for edge DDoS and WAF protection.
kubectl apply or deployment manifests.The primary mandates were sandboxing untrusted multi-tenant container code at the kernel syscall boundary, enforcing customer control over disk encryption keys at rest, and mitigating API data exfiltration.
This architecture combines Google Cloud's core compute hardening and isolation services: Confidential Computing, Shielded VMs/GKE Nodes, Binary Authorization, and Container-Optimized OS (COS) in a private cluster topology to establish an end-to-end trusted computing and workload isolation baseline.
This solution comprehensively addresses each technical layer—hardware memory encryption, boot-level verification, deployment-time image attestation, and hardened network isolation—without creating architectural gaps or relying on controls limited to data-at-rest.
This option uses Cloud Armor for layer 7 traffic inspection and WAF filtering, Web Security Scanner for discovering web-layer vulnerabilities (such as XSS and mixed content), Container Threat Detection (part of Security Command Center Premium) for runtime execution monitoring, and standard Ubuntu OS images on nodes.
The organization needed runtime intrusion detection for running containers and dynamic application security testing (DAST) for public-facing web services.
This option uses Artifact Analysis for automated container image vulnerability scanning, Cloud HSM (Hardware Security Modules) for FIPS 140-2 Level 3 cryptographic key management, Workload Identity Federation to grant Kubernetes service accounts fine-grained IAM permissions, and standard VM network provisioning.
The requirements focused on secret management FIPS compliance, fine-grained pod-to-GCP IAM authentication, and vulnerability reporting in container registries.
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