Examkin

Soru

Zorluk: OrtaModernizing Workloads using Containers (ECS and EKS)

StreamVibe is modernizing its legacy document-management application by migrating it to AWS. To minimize operational overhead, a solutions architect decides to deploy the containerized application on Amazon Elastic Container Service (Amazon ECS) using the AWS Fargate launch type. The application is distributed across three Availability Zones and requires a shared, persistent file system that supports simultaneous read and write operations with full POSIX-compliant file permissions. Which configuration should the solutions architect recommend to satisfy these requirements?

  1. Configure the ECS task definition to use the awsvpc network mode. Provision an Amazon Elastic File System (Amazon EFS) file system, and define an EFS volume in the task definition. Mount this volume to the container tasks, and utilize EFS Access Points to enforce POSIX permissions.Cevap
  2. B
    Configure the ECS task definition to use the bridge network mode. Provision an Amazon Elastic File System (Amazon EFS) file system, and define an EFS volume in the task definition. Mount this volume to the container tasks, and utilize EFS Access Points to enforce POSIX permissions.
  3. C
    Configure the ECS task definition to use the awsvpc network mode. Provision an Amazon Elastic Block Store (Amazon EBS) volume with Multi-Attach enabled. Configure the task definition to mount this EBS volume to the containers across the three Availability Zones.
  4. D
    Configure the ECS task definition to use the awsvpc network mode. Provision an Amazon Simple Storage Service (Amazon S3) bucket and configure the task definition to run a FUSE-based file system driver to mount the bucket. Route outbound traffic through a single NAT Gateway located in a single public subnet.

Cevap

Configure the ECS task definition to use the awsvpc network mode, provision an Amazon EFS file system, define an EFS volume in the task definition, mount this volume to the container tasks, and utilize EFS Access Points to enforce POSIX permissions.
The correct configuration uses the awsvpc network mode, which is the only network mode supported by the AWS Fargate launch type. It uses Amazon Elastic File System (Amazon EFS) to provide shared, regional storage that supports concurrent read and write operations across multiple Availability Zones. The configuration also leverages EFS Access Points to enforce specific POSIX user and group IDs, meeting the application's file permissions requirements.

Adım Adım Çözüm

1
Select the correct ECS launch type and networking mode.
AWS Fargate requires the awsvpc network mode, where every task receives its own Elastic Network Interface (ENI) and private IP address.
Fargate tasks do not share a host and therefore do not support host or bridge networking modes.
2
Determine the appropriate persistent storage type for concurrent multi-AZ access.
Select Amazon EFS, which is a regional service that allows concurrent read/write operations from multiple mounting points across multiple Availability Zones.
Amazon EBS is restricted to a single Availability Zone, and Amazon S3 does not natively support POSIX file system permissions.
3
Configure secure POSIX-compliant file access.
Create an EFS Access Point to enforce specific POSIX user IDs and group IDs for all application tasks mounting the file system.
EFS Access Points simplify directory permissions management for containerized workloads by overriding the user identity used to access the file system.

Anahtar Kavram

AWS Fargate network mode compatibility and regional shared persistent storage using Amazon EFS.
Bu soruyu puanla

Konular

Modernizing Workloads using Containers (ECS and EKS)

Bu konudan daha fazla soru