Q98 — AWS SAA-C03 Ch.14

Question 98 of 100 | ← Chapter 14

Q1098. A company is designing a new Amazon Elastic Kubernetes Service (Amazon EKS) deployment to host multi-tenant applications that use a single cluster. The company wants to ensure that each pod has its own hosted environment. The environments must not share CPU, memory,storage,or elastic network interfaces.Which solution will meet these requirements?

• A. Use Amazon EC2 instances to host self-managed Kubernetes clusters. Use taints and tolerations to enforce isolation boundaries.
• B. Use Amazon EKS with AWS Fargate.Use Fargate to manage resources and to enforce isolation boundaries. ✓
• C. Use Amazon EKS and self-managed node groups. Use taints and tolerations to enforce isolation boundaries.
• D. Use Amazon EKS and managed node groups. Use taints and tolerations to enforce isolation boundaries.

Correct Answer: B. Use Amazon EKS with AWS Fargate.Use Fargate to manage resources and to enforce isolation boundaries.

Explanation

To meet the requirements of ensuring that each pod in an Amazon Elastic Kubernetes Service (Amazon EKS) deployment has its own hosted environment, without sharing CPU, memory, storage, or elastic network interfaces, we need to consider the isolation capabilities provided by different deployment options.Let's evaluate each option:A. Use Amazon EC2 instances to host self-managed Kubernetes clusters. Use taints and tolerations to enforce isolation boundaries:While taints and tolerations can be used to enforce isolation within a Kubernetes cluster, this option still relies on EC2 instances for pod hosting.Pods running on the same EC2 instance would still share the CPU, memory, and storage resources of that instance, which violates the stated requirements.B. Use Amazon EKS with AWS Fargate:AWS Fargate allows you to run Kubernetes pods without having to manage servers or nodes. Each pod runs in its own isolated environment, with its own set of resources (CPU, memory, storage), and does not share these resources with other pods.Fargate pods also have their own elastic network interfaces, meeting all the isolation requirements. C. Use Amazon EKS and self-managed node groups. Use taints and tolerations to enforce isolation boundaries:Similar to option A, using self-managed node groups still involves pods sharing resources on the same nodes.Taints and tolerations can manage pod scheduling, but they do not provide the required hardware-level isolation.D. Use Amazon EKS and managed node groups. Use taints and tolerations to enforce isolation boundaries:Managed node groups simplify the management of nodes but do not change the fundamental sharing of resources between pods on the same node.Again, taints and tolerations are useful for scheduling but do not meet the hardware isolation requirements. Given these considerations, Option B (Use Amazon EKS with AWS Fargate) is the best solution to meet the stated requirements. Fargate provides the necessary isolation for each pod, ensuring that they do not share CPU, memory, storage, or elastic network interfaces.