300-745 practice question 9 of 15

A global energy company moved a monolithic application from the data center to public cloud. Over time, the company added many capabilities to the…

Full set: 58 questions
A global energy company moved a monolithic application from the data center to public cloud. Over time, the company added many capabilities to the application, and it is now difficult for the application team to scale it. The application owner decided to modernize the application by moving to a Kubernetes cluster. However, he wants to ensure that the new application architecture provides a container network interface that is scalable, offers options for cloud-native security, and helps with visibility and observability. Which solution must be used to accomplish the task?
Answer options
A: security group
B: Cilium Correct answer
C: ENI
D: ingress gateway
Correct Answer:
B. Cilium
Explanation

The question requires a solution for a Kubernetes environment that serves as a Container Network Interface (CNI) while also providing scalability, cloud-native security, visibility, and observability. Cilium is a CNI that leverages eBPF (extended Berkeley Packet Filter) to deliver high-performance networking directly within the Linux kernel. This architecture allows it to enforce advanced, identity-aware L3-L7 network security policies, provide deep visibility into network flows and application protocols through its Hubble component, and scale efficiently without the overhead of sidecar proxies or traditional IPtables. Cilium directly meets all the specified requirements for a modern, secure, and observable container network.

Why Incorrect

A. security group: This is a cloud provider's virtual firewall operating at the instance (VM) level, not a Kubernetes CNI providing pod-to-pod networking and observability.
C. ENI: An Elastic Network Interface is a virtual network card component in AWS. While used by some CNIs, it is not the CNI solution itself.
D. ingress gateway: An ingress gateway manages external traffic entering the cluster. It does not provide the fundamental pod-to-pod networking or cluster-wide security required of a CNI.

References

1. Cisco Solution for Kubernetes on AWS Design and Implementation Guide (CVD): In Chapter 4, "Network Design," under the "Container Network Interface" section, it states, "Cilium is a CNI plug-in for Kubernetes that can be used to implement the Kubernetes network model. Cilium provides advanced networking capabilities, such as API-aware network security filtering, transparent encryption, and extensive observability using BPF." This directly aligns with the requirements for security, observability, and its function as a CNI.

2. Official Cilium Documentation, "What is Cilium?": The introduction states, "Cilium is open source software for providing, securing, and observing network connectivity between container workloads... At the foundation of Cilium is a new Linux kernel technology called eBPF, which enables the dynamic insertion of powerful security, visibility, and networking control logic into the Linux kernel." This confirms its role in providing networking, security, and observability.

3. Official Kubernetes Documentation, "Network Plugins": This document defines the role of a CNI plugin as being "responsible for inserting a network interface into the container network namespace... and making any necessary changes on the host." This clarifies that options like security groups or ingress gateways do not fulfill the primary role of a CNI.

Scroll to Top