QuestionQ6

Resilient Cloud Solutions

A DevOps engineer is building infrastructure for an application. The application must run on an Amazon Elastic Kubernetes Service (Amazon EKS) cluster that contains Amazon EC2 instances. The EC2 instances must use an Amazon Elastic File System (Amazon EFS) file system as their storage backend. The Amazon EFS Container Storage Interface (CSI) driver is installed on the EKS cluster.

When the DevOps engineer starts the application, the EC2 instances fail to mount the EFS file system.

Which solutions will resolve the problem?

Choose three
  • A Switch the EKS nodes from Amazon EC2 to AWS Fargate.
  • B Add an inbound rule to the EFS file system’s security group to allow NFS traffic from the EKS cluster.
  • C Create an IAM role that allows the Amazon EFS CSI driver to interact with the file system
  • D Set up AWS DataSync to configure file transfer between the EFS file system and the EKS nodes.
  • E Create a mount target for the EFS file system in the subnet of the EKS nodes.
  • F Disable encryption or the EFS file system.
Explanation

EFS-backed Kubernetes volumes need an EFS mount target reachable from the EKS worker nodes, with the mount target’s security group allowing inbound NFS traffic on port 2049 from those nodes. The Amazon EFS CSI driver also needs IAM permissions to interact with the file system, such as permissions supplied by the AmazonEFSCSIDriverPolicy. A mount target must be available in the subnet/Availability Zone used by the EKS nodes.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!