Examkin

Question

Difficulty: MediumConfigure Azure Kubernetes Service (AKS)

Your company plans to deploy a new Azure Kubernetes Service (AKS) cluster named `aks-shipping`. You have an existing virtual network (`VNet1`) containing a subnet named `aks-subnet` with the address space 10.200.0.0/2410.200.0.0/24. Due to address space limitations, the corporate network team mandates that the cluster must not consume more than 150150 IP addresses from `aks-subnet`. The cluster must meet the following requirements:

* The cluster must scale up to a maximum of 8080 nodes.
* Each node must support up to 3030 pods.
* Pod IP addresses must be directly routable from an on-premises network via an ExpressRoute connection without performing Network Address Translation (NAT).

Which two configuration actions should you perform to meet these requirements? (Select two.)

  1. Configure the cluster network plugin to use Azure CNI.Answer
  2. Enable dynamic pod IP allocation and assign a separate subnet for pod IP addresses.Answer
  3. C
    Configure the cluster network plugin to use Kubenet.
  4. D
    Configure the cluster network plugin to use Azure CNI Overlay.
  5. E
    Deploy the cluster using standard Azure CNI without dynamic pod IP allocation.

Answer

To meet the requirements, the cluster network plugin must be configured to use Azure CNI, and dynamic pod IP allocation must be enabled with a separate subnet assigned for pod IP addresses.
To satisfy the direct routability requirement without NAT, the AKS cluster must use Azure CNI. To satisfy the constraint of not consuming more than 150150 IP addresses from the node subnet (`aks-subnet`) for 8080 nodes, you must enable dynamic pod IP allocation. This allows the nodes to be deployed in the node subnet (consuming only one IP address per node) and the pods to be deployed in a separate, dedicated subnet.

Step-by-Step Solution

1
Analyze the routing and NAT requirement.
Kubenet and Azure CNI Overlay are ruled out because they both use NAT for traffic leaving the nodes, which prevents pod IPs from being directly routable from the on-premises network.
The scenario requires pod IP addresses to be directly routable from the on-premises network via ExpressRoute without performing NAT.
2
Analyze the IP consumption limit on the node subnet.
Standard Azure CNI is ruled out because it pre-allocates IPs for pods directly from the node subnet. For 8080 nodes with 3030 pods each, this would consume over 24002400 IPs, exceeding the limit of 150150 IPs.
The node subnet `aks-subnet` has a limit of 150150 IP addresses for the cluster.
3
Select the configuration that combines VNet-routable IPs with minimized node subnet consumption.
Azure CNI with dynamic pod IP allocation satisfies both: nodes are placed in the node subnet (consuming 8080 IPs, under the 150150 limit), and pods are placed in a separate subnet (retaining direct VNet routing and on-premises reachability).
Dynamic pod IP allocation separates the node and pod subnets, allowing the node subnet to host only the nodes.

Key Concept

Azure CNI with Dynamic Pod IP Allocation
Rate this question

Topics

Configure Azure Kubernetes Service (AKS)

More questions from this topic