> For the complete documentation index, see [llms.txt](https://atomoh.gitbook.io/kubernetes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomoh.gitbook.io/kubernetes/en/quiz-collection/service-mesh/cilium-service-mesh/traffic-management.md).
# Traffic Management Quiz
This quiz tests your understanding of L7 traffic management, CiliumEnvoyConfig, load balancing, traffic splitting, and Gateway API integration in Cilium Service Mesh.
## Quiz Questions
### 1. Which Envoy filter is used to define HTTP routing rules in CiliumEnvoyConfig?
A. envoy.filters.network.tcp\_proxy B. envoy.filters.network.http\_connection\_manager C. envoy.filters.http.fault D. envoy.filters.network.redis\_proxy
Show Answer
**Answer: B. envoy.filters.network.http\_connection\_manager**
**Explanation:** The HTTP Connection Manager is the core Envoy filter for processing HTTP traffic. Within this filter, you can define path-based, header-based, and method-based routing rules through route\_config.
### 2. Which field is NOT available when defining L7 HTTP rules in CiliumNetworkPolicy?
A. method B. path C. headers D. body
Show Answer
**Answer: D. body**
**Explanation:** CiliumNetworkPolicy's HTTP L7 rules allow filtering based on method (HTTP method), path (URL path), and headers (HTTP headers). body (request body) is not supported in L7 rules.
### 3. Which is NOT a valid apiKey when applying Kafka L7 policies in Cilium?
A. produce B. fetch C. delete D. metadata
Show Answer
**Answer: C. delete**
**Explanation:** Cilium's Kafka L7 policies support apiKeys including produce (message production), fetch (message consumption), metadata (metadata queries), offsetcommit, offsetfetch, joingroup, etc. 'delete' is not a supported Kafka API key.
### 4. What is the advantage of Maglev hashing in Cilium's eBPF-based L4 load balancing?
A. Completely random distribution B. Session persistence even when backends change C. Lowest memory usage D. L7 routing support
Show Answer
**Answer: B. Session persistence even when backends change**
**Explanation:** Maglev is a consistent hashing algorithm that maintains most existing connections to the same backend even when backend servers are added or removed. This is useful for stateful applications or when session affinity is required.
### 5. What is the correct way to configure weight-based traffic splitting in Gateway API HTTPRoute?
A. Use the split field B. Specify weight field in backendRefs C. Use trafficPolicy D. Use destinationRule
Show Answer
**Answer: B. Specify weight field in backendRefs**
**Explanation:** In Gateway API HTTPRoute, traffic splitting is configured by specifying the weight field for each backend in the backendRefs array. For example, using `weight: 90` and `weight: 10` splits traffic in a 90:10 ratio.
### 6. Which is NOT a valid condition for the retry\_on field when configuring retry policies in CiliumEnvoyConfig?
A. 5xx B. reset C. timeout D. connect-failure
Show Answer
**Answer: C. timeout**
**Explanation:** Envoy's retry\_on conditions include 5xx (server errors), reset (connection reset), connect-failure (connection failure), retriable-4xx, etc. 'timeout' is not a direct retry\_on condition; per\_try\_timeout is used to set the timeout for each retry attempt.
### 7. What is the main benefit of using DNS L7 policies in Cilium?
A. Improved DNS server performance B. Allow only DNS queries for specific domains C. DNS cache invalidation D. DNS over HTTPS support
Show Answer
**Answer: B. Allow only DNS queries for specific domains**
**Explanation:** DNS L7 policies allow restricting which domains workloads can query. Using matchPattern or matchName, you can ensure only allowed domains are queried, preventing data exfiltration or access to malicious domains.
### 8. Which filter is used to configure local Rate Limiting in CiliumEnvoyConfig?
A. envoy.filters.http.ratelimit B. envoy.filters.http.local\_ratelimit C. envoy.filters.http.bandwidth\_limit D. envoy.filters.http.throttle
Show Answer
**Answer: B. envoy.filters.http.local\_ratelimit**
**Explanation:** Local Rate Limiting uses the envoy.filters.http.local\_ratelimit filter. This filter limits request rates through token\_bucket configuration. envoy.filters.http.ratelimit is used for global Rate Limiting that communicates with external Rate Limit services.
### 9. Which filter type is used to configure HTTP -> HTTPS redirect in Gateway API?
A. URLRewrite B. RequestMirror C. RequestRedirect D. ResponseHeaderModifier
Show Answer
**Answer: C. RequestRedirect**
**Explanation:** In Gateway API, the RequestRedirect filter is used to redirect from HTTP to HTTPS. Setting scheme: https and statusCode: 301 configures a permanent redirect.
### 10. What is the purpose of traffic mirroring (shadowing) in Cilium Service Mesh?
A. Traffic encryption B. Replicate production traffic to test environment C. Load balancing optimization D. Cache invalidation
Show Answer
**Answer: B. Replicate production traffic to test environment**
**Explanation:** Traffic mirroring sends a copy of production traffic to another service (e.g., a test environment with a new version). This allows testing new versions with real traffic without affecting users. It's configured through request\_mirror\_policies.
### 11. What is the role of total\_weight in canary deployment using weighted\_clusters in CiliumEnvoyConfig?
A. Limit total request count B. Define the reference value for weight sum C. Timeout setting D. Connection limit
Show Answer
**Answer: B. Define the reference value for weight sum**
**Explanation:** total\_weight defines the reference value for the sum of individual cluster weights. For example, setting total\_weight: 100 and assigning 90 to cluster A and 10 to cluster B results in 90% and 10% traffic respectively.
### 12. Which field is used in the matches section to configure header-based routing in Gateway API HTTPRoute?
A. headerMatchers B. headers C. requestHeaders D. matchHeaders
Show Answer
**Answer: B. headers**
**Explanation:** In HTTPRoute's matches section, the headers field is used to configure header-based routing. By specifying name and value for each header, you can route requests with specific header values to different backends.