Examkin

Soru

Zorluk: ZorAWS Elastic Beanstalk

A development team is preparing to update an application hosted on AWS Elastic Beanstalk. The new version requires the installation of an OS-level utility (xml2) on the underlying EC2 instances. Additionally, to guarantee clean system states, the team requires that the update is only applied to newly provisioned instances rather than modifying the existing ones in-place. The update must maintain the application's full serving capacity throughout the deployment process, but the team wants to avoid performing a manual DNS redirection or CNAME swap. Which two configuration steps should the developer perform to meet these requirements? (Select TWO.)

  1. Create a configuration file inside a directory named .ebextensions at the root level of the application source bundle to install the package.Cevap
  2. Configure the deployment policy for the environment to use Immutable updates.Cevap
  3. C
    Create a configuration file inside a directory named ebextensions at the root level of the application source bundle to install the package.
  4. D
    Configure the deployment policy for the environment to use Rolling with additional batch updates.
  5. E
    Configure the deployment policy for the environment to use Rolling updates.

Cevap

To meet the requirements, the developer must create a configuration file inside a directory named .ebextensions at the root level of the application source bundle, and configure the environment's deployment policy to use Immutable updates.
To satisfy the requirement of installing custom OS-level packages, the configuration file must be placed inside the .ebextensions directory at the root level of the source bundle. To satisfy the deployment requirements (clean instances, full serving capacity, and no manual CNAME swap), the Immutable deployment policy must be used. This policy provisions a secondary Auto Scaling group with the new version, merges it with the existing group once healthy, and then terminates all the old instances, ensuring no configuration residue exists.

Adım Adım Çözüm

1
Determine the correct directory structure for Elastic Beanstalk customization files.
Identify that custom packages must be defined under a .ebextensions folder at the root level of the application source bundle.
Elastic Beanstalk ignores configuration folders that lack the leading dot, such as ebextensions.
2
Evaluate the deployment strategies against the zero-downtime, no CNAME-swap, and clean-instance constraints.
Identify that Immutable deployment provisions a temporary Auto Scaling group with new instances, validates health, and then merges them, terminating the old instances.
Rolling and Rolling with additional batch strategies update existing instances in-place, which leaves configuration residue. A CNAME swap requires manual environment creation and DNS redirection, which is forbidden by the scenario constraints.

Anahtar Kavram

AWS Elastic Beanstalk configuration files (.ebextensions) and environment deployment policies.
Bu soruyu puanla

Konular

AWS Elastic Beanstalk

Bu konudan daha fazla soru