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 operates a sensitive multi-tier financial application running across multiple namespaces on Google Kubernetes Engine (GKE). To comply with a zero-trust security framework, the architecture must satisfy two core requirements:
Which combination of controls should the security team implement to satisfy these requirements?
This approach uses Cloud Service Mesh's default PERMISSIVE authentication mode alongside standard VPC firewall rules that target Compute Engine VM instance network tags on the underlying GKE nodes.
PERMISSIVE mode, sidecar proxies accept both mTLS and unencrypted plaintext traffic. This fails the mandate to reject all plaintext connections across tiers.PERMISSIVE mode: Primarily intended for transitional migration phases while onboarding services to a service mesh.The organization were executing an initial phased migration to Cloud Service Mesh where legacy workloads without sidecars still needed plaintext access while node-level perimeter filtering was sufficient.
This architecture combines Cloud Service Mesh transport authentication controls with native Kubernetes NetworkPolicy resources to create a defense-in-depth, zero-trust boundary around containerized microservice tiers in GKE.
PeerAuthentication custom resource with spec.mtls.mode: STRICT (either across the mesh in the istio-system root namespace or per workload namespace) ensures that the sidecar proxies mandate mutual TLS. Plaintext traffic and unauthenticated requests are actively blocked at the application/transport layer.NetworkPolicy objects enforce container-level packet filtering. By leveraging podSelector and namespaceSelector, security teams specify exact ingress and egress whitelists, ensuring that only explicitly authorized Pods can establish network connections to sensitive backend tiers.Combining PeerAuthentication in STRICT mode with Kubernetes NetworkPolicies addresses both transport-layer data encapsulation and network-level microsegmentation. It prevents lateral movement from compromised Pods while guaranteeing that all in-flight microservice data is cryptographically secure.
This setup utilizes Binary Authorization to ensure only cryptographically signed container images are deployed by the GKE admission controller, combined with Cloud Armor layer 7 security policies attached to backend services on an Internal Application Load Balancer.
The primary objective were securing the software supply chain against untrusted container images and protecting external-facing HTTP endpoints from web-based vulnerabilities and DDoS attacks.
This approach uses an Istio DestinationRule with TLS disabled on the client sidecar proxies and attempts to achieve inter-tier encryption using Cloud VPN IPsec tunnels between the underlying GKE node subnets.
tls.mode: DISABLE explicitly instructs client proxies to send cleartext HTTP requests, completely bypassing mutual TLS identity assertions.tls.mode: DISABLE: Prevents sidecar proxies from initiating mTLS handshakes, exposing microservice communication to plaintext transmission within the node.The requirement were connecting two distinct remote VPC networks over the public internet using IPsec while managing unencrypted legacy backend workloads.
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