The answer is to enable Anthos Service Mesh with mutual TLS (mTLS) across clusters. This is correct because mTLS provides authenticated, encrypted communication at the application layer between pods in different GKE clusters, ensuring that cardholder data in transit meets PCI DSS encryption requirements. Unlike network-level encryption alone, mTLS verifies the identity of both sides of the connection with certificates, preventing man-in-the-middle attacks and allowing fine-grained policy enforcement across multi-cluster deployments. On the Google Professional Cloud Security Engineer exam, this scenario tests your understanding of how to encrypt inter pod traffic GKE PCI DSS requirements in a multi-region architecture. A common trap is choosing a simpler option like GKE Dataplane V2 or network policies, which only encrypt at the IP layer and lack identity verification. Remember the mnemonic: “mTLS = mutual trust + layer security” — both sides must prove who they are before data moves.
PCSE Supporting compliance requirements Practice Question
This PCSE practice question tests your understanding of supporting compliance requirements. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A financial services company is deploying a multi-region application on Google Kubernetes Engine (GKE) and needs to comply with PCI DSS. They must ensure that cardholder data is encrypted in transit between pods in different clusters. What is the MOST secure way to achieve this?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable Anthos Service Mesh with mutual TLS (mTLS) across clusters.
Option B is correct because Anthos Service Mesh with mutual TLS (mTLS) provides authenticated and encrypted communication between pods across different GKE clusters, meeting PCI DSS encryption-in-transit requirements. mTLS ensures that each side of the connection presents a certificate, verifying identity and encrypting traffic at the application layer, which is more secure than relying solely on network-level encryption. This approach also integrates with GKE's multi-cluster service mesh capabilities, allowing fine-grained policy enforcement across clusters.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Configure TLS for each service using a Cloud Load Balancing with SSL policies.
Why it's wrong here
Cloud Load Balancing is for external traffic, not for pod-to-pod communication within the mesh.
✓
Enable Anthos Service Mesh with mutual TLS (mTLS) across clusters.
Why this is correct
mTLS in a service mesh provides encryption and authentication for inter-pod traffic.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use HTTPS between services by configuring ingress with a Google-managed SSL certificate.
Why it's wrong here
HTTPS is for external traffic; pods communicate internally over HTTP/gRPC.
✗
Use VPC Network Peering to connect the clusters and rely on the internal network encryption.
Why it's wrong here
VPC peering does not encrypt traffic; encryption must be applied at the application layer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that network-level encryption (e.g., VPC peering or internal Google Cloud encryption) is sufficient for compliance, but PCI DSS requires application-layer encryption (e.g., TLS/mTLS) for cardholder data in transit between pods.
Detailed technical explanation
How to think about this question
Anthos Service Mesh uses Envoy sidecar proxies to intercept all pod traffic and enforce mTLS, leveraging SPIFFE-compliant identities for workload authentication. Under the hood, it negotiates TLS 1.3 with mutual authentication, and the encryption keys are rotated automatically via the mesh's certificate authority (CA), typically using Istio's Citadel or a pluggable CA. In a real-world scenario, if a pod is compromised, mTLS prevents lateral movement because the attacker's pod lacks the correct workload identity certificate to communicate with other services.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Supporting compliance requirements — This question tests Supporting compliance requirements — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable Anthos Service Mesh with mutual TLS (mTLS) across clusters. — Option B is correct because Anthos Service Mesh with mutual TLS (mTLS) provides authenticated and encrypted communication between pods across different GKE clusters, meeting PCI DSS encryption-in-transit requirements. mTLS ensures that each side of the connection presents a certificate, verifying identity and encrypting traffic at the application layer, which is more secure than relying solely on network-level encryption. This approach also integrates with GKE's multi-cluster service mesh capabilities, allowing fine-grained policy enforcement across clusters.
What should I do if I get this PCSE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PCSE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCSE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.