Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing an automated data ingestion pipeline where external applications running on an on-premises platform need to upload analytics datasets into Google Cloud resources. The security architecture team has established two strict compliance requirements:
Which architecture should you implement to satisfy these security requirements?
This option relies on generating standard service account JSON private keys, storing them inside Secret Manager, and configuring Google Cloud Armor to inspect and filter network traffic directed at external endpoints.
The requirement were to protect a custom public-facing web service hosted behind an External Application Load Balancer from Layer 7 injection attacks using centralized application secrets.
Workload Identity Federation is an identity mechanism that allows workloads running outside Google Cloud (such as on-premises environments or other cloud platforms) to impersonate IAM service accounts and obtain short-lived OAuth 2.0 access tokens using industry-standard protocols like OpenID Connect (OIDC) or SAML 2.0. VPC Service Controls is a resource-centric security perimeter capability that defines boundaries around Google Cloud services and APIs to mitigate data exfiltration risks and block unauthorized access from outside trusted perimeters.
Combining Workload Identity Federation with VPC Service Controls is the recommended architecture for enterprise integrations. It directly resolves the dual challenge of eliminating static credential storage at the identity layer while establishing strict perimeter boundaries that prevent data exfiltration at the network and API layers.
Cloud Identity Single Sign-On (SSO) integrates corporate identity providers (such as Microsoft Entra ID, Okta, or Active Directory) with Google Cloud to authenticate human users. Access Context Manager access bindings enforce context-aware requirements (such as device posture or IP range) directly onto Cloud Identity user groups.
The organization needed to govern administrative console access for human developers using corporate SSO credentials and enforce device verification before granting console access.
Cloud Service Mesh with Identity-Aware Proxy (IAP) token exchange provides edge ingress authentication by exchanging external JSON Web Tokens (JWTs) for short-lived mesh-internal tokens (RequestContextToken) to defend against token replay attacks within a Kubernetes service mesh. Kubernetes Network Policies filter IP and port communications at Layer 3 and Layer 4 between Pods.
You needed to protect a containerized microservice running on Google Kubernetes Engine (GKE) from token replay attacks and enforce micro-segmentation between application pods.
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