AWS - EKSWhy does the AWS VPC CNI plugin assign IP addresses from the VPC subnet directly to pods instead of using an overlay network?ATo provide high performance and native VPC networking for podsBBecause overlay networks are not supported in KubernetesCTo simplify pod security by disabling network policiesDTo reduce the number of IP addresses used by podsCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand the benefit of direct VPC IP assignmentAssigning IPs directly from the VPC subnet gives pods native VPC networking, improving performance and compatibility.Step 2: Eliminate incorrect reasonsOverlay networks are supported in Kubernetes; VPC CNI does not disable network policies; direct assignment does not reduce IP usage.Final Answer:To provide high performance and native VPC networking for pods -> Option AQuick Check:Direct VPC IPs = native networking and better performance [OK]Quick Trick: Direct VPC IPs give pods native, fast networking [OK]Common Mistakes:Believing overlay networks are unsupportedThinking VPC CNI disables network policiesAssuming direct IP assignment reduces IP count
Master "EKS" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Architecture Best Practices - Operational excellence pillar - Quiz 9hard Architecture Best Practices - Multi-tier architecture patterns - Quiz 11easy Architecture Best Practices - Cost optimization pillar - Quiz 8hard CloudFormation - CloudFormation vs Terraform awareness - Quiz 1easy CloudFormation - Template structure (JSON/YAML) - Quiz 13medium ECS and Fargate - Fargate vs EC2 launch type - Quiz 14medium ECS and Fargate - Fargate vs EC2 launch type - Quiz 12easy ECS and Fargate - Fargate vs EC2 launch type - Quiz 5medium ECS and Fargate - Services and tasks - Quiz 8hard EKS - Why managed Kubernetes matters - Quiz 15hard