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 enterprise is deploying sensitive workloads to Google Cloud and must satisfy strict data sovereignty and jurisdictional isolation regulations. The enterprise security policy requires that the root-of-trust encryption keys reside exclusively within on-premises Hardware Security Modules (HSMs) outside Google Cloud. Furthermore, all cryptographic communication between Google Cloud services and the on-premises key management systems must traverse private network paths without traversing the public internet, while supporting automated failover between dual on-premises data centers.
Which Cloud External Key Manager (Cloud EKM) architecture should the organization implement?
This architecture attempts to establish a direct connection between Cloud EKM and an on-premises external key manager over private hybrid connectivity while placing keys in a multi-regional Cloud KMS key ring.
Cloud KMS supported multi-regional key rings over VPC networks and the organization required a direct-connect topology without intermediate load balancer layers.
Cloud External Key Manager (Cloud EKM) over a VPC network enables Google Cloud services to protect data at rest using encryption keys maintained directly inside a customer's external, on-premises key management infrastructure. Instead of sending requests across the public internet, cryptographic requests travel over private hybrid connectivity such as Cloud Interconnect or HA VPN.
This architecture satisfies both sovereign key custody outside Google Cloud and strict network perimeter requirements by pairing private hybrid connectivity with an internal load balancer in a regional configuration.
Single-tenant Cloud HSM provides dedicated, physical HSM partitions inside Google Cloud data centers, managed jointly by the organization and Google, with access bounded by VPC Service Controls perimeters.
The organization wanted dedicated, hardware-isolated cryptographic modules hosted directly within Google Cloud data centers rather than retaining keys in an external on-premises datacenter.
This architecture establishes a Cloud EKM over the internet deployment using an external proxy Network Load Balancer with hybrid connectivity Network Endpoint Groups (NEGs) to distribute cryptographic requests across external key management systems.
The organization required multi-regional Cloud KMS keys accessible over the public internet with global Anycast routing rather than private VPC connectivity and regional isolation.
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