CCSP Cloud Application Security Practice Question
A security architect is designing a cloud-native application using microservices. They decide to implement mutual TLS (mTLS) for service-to-service communication in a Kubernetes cluster with hundreds of services. What is the primary challenge in managing mTLS certificates in this dynamic environment?
⚠ Common exam trap
Test-takers frequently confuse the operational challenge of certificate lifecycle management with perceived performance issues (latency) or compatibility concerns, when in fact mTLS is designed to work efficiently with modern protocols and the real difficulty is maintaining trust in a rapidly changing service mesh.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Certificate revocation and rotation
In a dynamic Kubernetes environment with hundreds of microservices, mTLS certificates must be frequently rotated and revoked to maintain security, especially as services scale up/down and pods are replaced. Manual certificate management is impractical, so automated solutions like SPIFFE/SPIRE or Istio’s Citadel are required to handle the lifecycle at scale. The primary challenge is not the encryption overhead but the operational complexity of ensuring every service has a valid, non-expired certificate and that compromised certificates can be promptly revoked across the mesh.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
High latency due to encryption overhead
Why it's wrong here
TLS handshake and symmetric encryption overhead is negligible relative to typical service call latency, so it is not the primary challenge. Latency concerns are tempting because encryption does consume CPU cycles, and they would matter for extremely high-throughput, latency-sensitive workloads where every millisecond counts.
- ✓
Certificate revocation and rotation
Why this is correct
Hundreds of short-lived pods mean certificates expire and rotate constantly, so revocation and rotation at scale becomes the operational bottleneck. Manual or static PKI cannot track ephemeral workload identities, making automated issuance and revocation the primary management challenge in this dynamic Kubernetes environment.
- ✗
Incompatibility with HTTP/2
Why it's wrong here
mTLS operates beneath HTTP/2 and is fully compatible with it; HTTP/2 mandates TLS in practice, and mTLS simply adds client certificate verification. The incompatibility claim is tempting because TLS interception and some proxies can disrupt HTTP/2 framing, but that is a proxy misconfiguration, not an mTLS limitation.
- ✗
Increased complexity in load balancer configuration
Why it's wrong here
Load balancers terminate or pass through TLS regardless of client certificates, so configuration complexity there is not the core problem. It is tempting because TLS termination settings do involve certificate handling, and that would be the answer if the question concerned ingress traffic rather than hundreds of ephemeral service identities.
Go deeper
Related to this question
About these practice questions
One of 934 original CCSP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CCSP practice question is part of Courseiva's free ISC2 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 CCSP exam.