KCNA Service Mesh 5

Question 1

Which CNCF project provides a specification for defining service mesh interfaces so applications can work with multiple mesh implementations?

Accepted Answer

SMI (Service Mesh Interface)

Answer

SMI provides a standard set of Kubernetes CRDs for traffic management, observability, and access control that work across different mesh implementations.

Question 2

What is 'traffic splitting' in a service mesh primarily used for?

Accepted Answer

Distributing traffic between two or more service versions for A/B testing or progressive delivery

Answer

Traffic splitting lets you route a defined percentage of requests to different service versions, enabling A/B tests and progressive rollouts.

Question 3

In service mesh observability, what are the 'golden signals' that SREs typically monitor?

Accepted Answer

Latency, traffic, errors, saturation

Answer

Google SRE's four golden signals — latency, traffic, errors, and saturation — are the core metrics a service mesh surfaces per service.

Question 4

Which Flagger feature automatically rolls back a canary deployment when error rate or latency thresholds are exceeded?

Accepted Answer

Progressive delivery with automated analysis

Answer

Flagger performs automated canary analysis by comparing metrics against thresholds and rolling back if the canary fails.

Question 5

What is the key advantage of using a service mesh for retries compared to implementing retries in application code?

Accepted Answer

The mesh handles retries transparently without modifying application code

Answer

Service mesh retries are implemented in the proxy layer, so applications need no changes and retry logic is consistently applied across all services.

(KCNA) Kubernetes and Cloud Native Associate Practice Test

(KCNA) Kubernetes and Cloud Native Associate Practice Test

KCNA Service Mesh 5