Service Mesh KCSA Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   What is a common performance overhead consideration when adopting a service mesh?

   • AReduced availability due to control plane failures
   • BDecreased network bandwidth due to encryption
   • CIncreased latency due to additional proxy hops
   • DIncreased storage requirements for logs
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which observability feature provided by a service mesh allows you to track a request as it travels through multiple microservices?

   • AService discovery
   • BLog aggregation
   • CMetrics collection
   • DDistributed tracing
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A security team wants to ensure that all service-to-service communication is encrypted and authenticated. They have a service mesh. What is the most secure configuration?

   • AEnable mTLS with STRICT mode and use AuthorizationPolicy to restrict access.
   • BEnable mTLS with PERMISSIVE mode to allow both HTTP and HTTPS traffic.
   • CUse only AuthorizationPolicy without mTLS.
   • DRely on the application to implement its own TLS.
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A company is considering adopting a service mesh for a large microservices environment. They are concerned about performance overhead and operational complexity. They want to minimize the impact on existing applications. What is the most important consideration?

   • AThe service mesh will require rewriting all application code to use its APIs.
   • BThe sidecar proxy adds latency to every service-to-service call, and the control plane adds operational overhead.
   • CThe service mesh will replace the need for Kubernetes NetworkPolicies and Ingress controllers.
   • DThe service mesh will automatically secure all traffic without any configuration changes.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A security team wants to ensure that all service-to-service communication is encrypted using mTLS. They have deployed a service mesh. What is the most efficient way to enforce this?

   • ACreate a NetworkPolicy that allows only TLS traffic on port 443.
   • BUse a Kubernetes Secret to distribute certificates to each pod and configure the application to use them.
   • CEnable mesh-wide mTLS by setting a global PeerAuthentication policy to STRICT.
   • DConfigure each service to use HTTPS by modifying the application code.
   Reveal Solution Discussion Select an answer first