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 is deploying an AI agent solution built on the Gemini platform on Google Cloud. The architecture processes real-time user prompts, retrieves context from backend storage, and persists conversation history and model outputs.
The security team mandates the following compliance and data governance requirements:
europe-west1 region and be prevented from crossing virtual network boundaries.Which combination of security controls should the security engineer implement?
content.deidentify method targeting the dlp.europe-west1.rep.googleapis.com regional endpoint; enforce the constraints/gcp.restrictEndpointUsage and constraints/gcp.resourceLocations organization policies; enclose services within a VPC Service Controls perimeter; and configure CMEK using Cloud KMS keys created in europe-west1.This architecture combines Sensitive Data Protection (Cloud DLP) regional endpoints, VPC Service Controls, Cloud KMS, and Organization Policy Service constraints to establish end-to-end data governance, strict data residency, and encryption for AI workloads.
content.deidentify API method of Cloud DLP inspects and de-identifies prompt strings and model responses in real time before data reaches persistent backend storage.dlp.europe-west1.rep.googleapis.com ensures that TLS sessions terminate inside europe-west1, guaranteeing that data at rest, in use, and in transit never leaves the specified region. Enforcing constraints/gcp.restrictEndpointUsage prevents client calls from accidentally routing to global endpoints.constraints/gcp.resourceLocations limits resource provisioning strictly to europe-west1 across all projects.europe-west1 wrap local data encryption keys (DEKs) ensuring full customer control over encryption at rest.content methods sanitizes generative AI inputs and outputs before storage.locations/europe-west1/content:deidentify; apply the constraints/gcp.resourceLocations organization policy; configure default Google-managed encryption keys; and rely on Cloud Armor WAF rules to restrict API egress across regions.This configuration calls the global Cloud DLP API endpoint (dlp.googleapis.com) while supplying a processing location in the URI path (/locations/europe-west1), relying on Google-default encryption and Cloud Armor.
europe-west1.constraints/gcp.restrictEndpointUsage, clients can route sensitive payload traffic globally.The organization had no requirement for in-transit regional residency, did not require CMEK, and served external public web traffic needing Layer 7 DDoS mitigation.
europe; and use Serverless VPC Access connectors without VPC Service Controls perimeters.This option sets up batch inspection jobs on persistent Cloud Storage buckets, configures Cloud KMS across multi-region europe, and relies on Serverless VPC Access.
europe violates the strict requirement to confine data and cryptographic keys specifically to europe-west1.The organization needed periodic batch discovery across historical training archives without real-time sanitization or single-region residency constraints.
This option configures Private Services Access via VPC Network Peering, uses Cloud Storage Bucket Lock for retention, and uses Cloud KMS asymmetric digital signature keys.
RSA_SIGN, ECDSA, PQC) validate message integrity and non-repudiation, not payload transformation or tokenization.The primary goal was enforcing immutable retention on audit log archives and verifying digital signatures on API message exchanges.
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