Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization operates a microservices-based payment platform on Google Kubernetes Engine (GKE) using Cloud Service Mesh with Istio APIs. Currently, the mesh uses default auto mTLS settings, and internal services communicate without explicit access restrictions.
To meet compliance standards, you must update the architecture with the following requirements:
payments service so that only the billing service can send POST requests to the /admin path, while denying all other service requests by default.Which configuration should you implement?
PERMISSIVE mTLS mode so sidecars automatically encrypt mesh traffic, configure a Kubernetes NetworkPolicy allowing ingress to the payments Pods only from the billing Pod IP ranges on the service port, and monitor denied connections using GKE VPC Flow Logs.Permissive mTLS (enabled by default with auto mTLS) instructs client sidecars to send encrypted mTLS traffic to peers that also have sidecars, while allowing server workloads to accept both mTLS and plaintext connections. A Kubernetes NetworkPolicy is a cluster-level firewall specification that controls Layer 3 and Layer 4 network traffic based on Pod labels, namespaces, IP blocks, and ports.
PERMISSIVE mode, the payments service still accepts unauthenticated plaintext requests, violating the requirement to strictly reject non-mTLS traffic.NetworkPolicy operates strictly at Layers 3 and 4, it cannot inspect HTTP attributes such as the /admin URL path or the POST method. Any allowed Pod could call any endpoint or HTTP verb on the payments port.principals) or Layer 7 authorization policy denials.NetworkPolicy governs TCP/UDP packet flow by IP and port rather than application-layer payloads.STRICT mode, workloads without sidecars can still send plaintext traffic to mesh services.The requirement was solely to restrict Layer 3/4 port connectivity between namespaces or block UDP traffic during an incremental mesh migration where plaintext fallback was still temporarily required.
Zero-trust microservice security relies on decoupling identity from network location. Relying on IP addresses and PERMISSIVE mode leaves services vulnerable to plaintext injection and coarse-grained access.
DestinationRule with tls.mode: ISTIO_MUTUAL in the payments namespace, attach a Google Cloud Armor security policy to enforce Layer 7 /admin path and POST method rules between internal services, and review blocked requests in Cloud Armor logs.A DestinationRule configures client-side traffic policies—including outbound TLS origination (ISTIO_MUTUAL), load balancing, and connection pooling—applied by calling sidecars after routing occurs. Google Cloud Armor is an external Web Application Firewall (WAF) and DDoS protection service deployed on Cloud Load Balancing at the network edge.
DestinationRule only instructs client proxies to initiate mTLS; it does not configure the payments server proxy to reject plaintext connections, which requires a server-side PeerAuthentication policy in STRICT mode.DestinationRule policies govern how outbound traffic is sent, not what inbound traffic a server accepts.AuthorizationPolicy resources evaluated by Envoy sidecars.The goal was to protect a public-facing ingress load balancer from external DDoS and Layer 7 injection attacks while ensuring outbound sidecar clients initiate mTLS to a specific service.
A defense-in-depth mesh architecture pairs Cloud Armor at the ingress edge with PeerAuthentication and AuthorizationPolicy inside the cluster to secure both north-south and east-west traffic.
PeerAuthentication in PERMISSIVE mode, create a single DENY AuthorizationPolicy on the payments service blocking requests to /admin that do not originate from the billing Pod CIDR range, and inspect application container STDOUT logs to audit client identities.An AuthorizationPolicy with action: DENY explicitly blocks incoming requests that match its defined rules, taking precedence over ALLOW policies. When paired with source filters, it attempts to blacklist specific undesirable traffic patterns while permitting traffic that does not match the denial criteria.
PeerAuthentication in PERMISSIVE mode allows unencrypted plaintext requests to reach the payments service unless explicitly blocked.DENY rule for /admin leaves all other endpoints and HTTP methods open to every caller in the cluster, instead of denying all access by default. Additionally, filtering by Pod CIDR ranges instead of mTLS principals fails to provide identity-based security because Pod IPs are ephemeral.STDOUT logs do not record mesh policy enforcement status, denied requests dropped at the Envoy sidecar proxy before reaching the container, or cluster-wide security posture.DENY policies are evaluated before ALLOW policies, and matching a DENY rule immediately rejects the request with HTTP 403.DENY rules on specific attributes without a baseline allow-nothing policy makes it easy for attackers to bypass rules using unexpected paths or host headers.You already had STRICT mTLS and an allow-nothing baseline in place and needed a temporary emergency DENY rule to block a specific compromised identity or path.
Best practices dictate starting with an allow-nothing AuthorizationPolicy and incrementally granting ALLOW rules based on verified Kubernetes Service Account principals rather than IP ranges.
PeerAuthentication policy in the istio-system namespace with mtls.mode set to STRICT. Assign dedicated Kubernetes Service Accounts to each workload, apply an allow-nothing AuthorizationPolicy paired with an ALLOW AuthorizationPolicy granting the billing principal POST access to /admin, and monitor identities and denials through Google Cloud Observability and the GKE Enterprise Security dashboard.Cloud Service Mesh implements a zero-trust security model at the data plane using sidecar proxies to manage mutual TLS (mTLS) and Layer 7 authorization without requiring application code changes. A mesh-wide PeerAuthentication resource enforces cryptographic workload authentication, while AuthorizationPolicy resources control access based on verified SPIFFE service identities rather than ephemeral IP addresses.
PeerAuthentication policy without a selector in the root istio-system namespace with mtls.mode: STRICT overrides the default PERMISSIVE behavior across the mesh, ensuring every workload rejects unencrypted plaintext traffic.action: ALLOW with no rules) establishes a default-deny baseline, and adding an explicit ALLOW rule restricts POST requests on /admin solely to the billing service's principal.Combining mesh-wide STRICT PeerAuthentication, a default-deny AuthorizationPolicy baseline with principal-scoped ALLOW rules, and built-in mesh telemetry directly satisfies transport security, Layer 7 least privilege, and identity-aware auditing in a unified, zero-trust architecture.
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