Examkin

Deployment Strategies

83 soru

Tüm türler83Çoktan seçmeli41Çoklu seçim42
Soru 61Soru →

A developer needs to update a web application running on an AWS Elastic Beanstalk environment. The update must be performed with zero downtime. Due to strict budget constraints, the environment must not provision any additional Amazon EC2 instances during the deployment process. The development team is willing to accept a temporary reduction in application capacity while the update is in progress. Which deployment strategy should the developer configure?

Cevabı ve açıklamayı göster

Cevap: Rolling

Cevap

Rolling
The Rolling deployment strategy updates instances in-place in batches. Because it uses the existing instances to perform the update and does not launch additional instances, it complies with the budget constraint. It keeps the remaining instances in service during the batch updates, satisfying the zero-downtime requirement at the expense of a temporary reduction in capacity.

Adım Adım Çözüm

1
Analyze the requirements and constraints in the scenario.
Requirements identified: 1. Zero downtime. 2. No additional EC2 instances allowed due to budget. 3. Temporary capacity reduction is acceptable.
Understanding the constraints is necessary to eliminate unsuitable deployment options.
2
Evaluate the available AWS Elastic Beanstalk deployment policies against the constraints.
All-at-once causes downtime. Immutable and Rolling with additional batch launch new EC2 instances. Rolling updates existing instances in batches without provisioning extra instances.
To find the strategy that satisfies both zero-downtime and zero additional instance creation.
3
Select the strategy that meets all constraints.
Rolling is the correct selection as it updates instances in-place in batches, incurring no extra instance costs and maintaining service availability at reduced capacity.
Ensures the selected option fulfills the application requirements.

Anahtar Kavram

AWS Elastic Beanstalk deployment policies allow developers to balance application availability, capacity, and cost during updates.
Soru 62Soru →

A developer is using AWS CodeDeploy to perform an in-place deployment of an application to an EC2 Auto Scaling group containing 44 running instances. The application must maintain at least 75%75\% of its traffic-serving capacity during the deployment process to handle regular user traffic. The developer also wants to avoid launching any new EC2 instances to minimize additional costs.

Which of the following CodeDeploy configurations will meet these requirements? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: The CodeDeployDefault.OneAtATime default deployment configuration; A custom deployment configuration with the minimum healthy hosts parameter set to a host count of 33

Cevap

The correct configurations are the CodeDeployDefault.OneAtATime default deployment configuration and a custom deployment configuration with the minimum healthy hosts parameter set to a host count of 33.
The correct options are the default configuration that updates one host at a time and the custom configuration that specifies a minimum of 33 healthy hosts. With a desired capacity of 44 instances, maintaining 75%75\% capacity means at least 33 instances must remain online and healthy during the deployment. The configuration that deploys to one instance at a time will update exactly 11 instance, leaving 33 active (75%75\%). Similarly, setting the custom minimum healthy hosts to a host count of 33 explicitly forces CodeDeploy to maintain 33 healthy instances throughout the process.

Adım Adım Çözüm

1
Calculate the number of healthy instances required to meet the 75%75\% capacity threshold.
For a fleet of 44 instances, 75%75\% capacity requires at least 33 instances to remain healthy and online (4×0.75=34 \times 0.75 = 3).
To understand the minimum healthy host constraint needed for the deployment configuration.
2
Analyze the default and custom CodeDeploy configurations against the calculated constraint.
CodeDeployDefault.OneAtATime updates 11 instance at a time, leaving 33 online (75%75\%). A custom configuration with minimum healthy hosts set to a host count of 33 explicitly guarantees 33 online instances.
To identify which specific configurations satisfy the target constraint of keeping at least 33 instances healthy.

Anahtar Kavram

AWS CodeDeploy deployment configurations and minimum healthy hosts settings for EC2 deployments
Soru 63Soru →

A developer is setting up a blue/green deployment for a containerized application running on Amazon ECS using AWS CodeDeploy. The deployment must route 10%10\% of the production traffic to the new version of the application immediately. The remaining 90%90\% of the traffic must be routed to the new version only after a 1515-minute validation period, during which the application's health is monitored. If any errors occur during this period, CodeDeploy must automatically roll back the deployment.

Which pre-defined CodeDeploy deployment configuration should the developer use to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: CodeDeployDefault.ECSCanary10Percent15Minutes

Cevap

CodeDeployDefault.ECSCanary10Percent15Minutes
The configuration CodeDeployDefault.ECSCanary10Percent15Minutes is correct because it is a pre-defined CodeDeploy deployment configuration designed for Amazon ECS. It shifts 10%10\% of traffic to the replacement task set immediately, waits for 1515 minutes for validation and monitoring, and then routes the remaining 90%90\% of traffic to the new version.

Adım Adım Çözüm

1
Identify the target compute platform.
The application runs on Amazon ECS, so the configuration name must begin with CodeDeployDefault.ECS.
CodeDeploy has separate pre-defined configurations for ECS, Lambda, and EC2/On-Premises.
2
Determine the traffic shifting pattern.
The requirement is to shift a small portion (10%10\%) and then the rest after a delay, which corresponds to a Canary deployment pattern.
Linear configurations shift traffic in equal increments at regular intervals, whereas Canary configurations shift an initial percentage, wait for a specified time, and then shift all remaining traffic.
3
Match the specified percentage and time interval parameters.
The parameters are 10%10\% traffic shifted immediately and a 1515-minute wait time, which matches CodeDeployDefault.ECSCanary10Percent15Minutes.
This is a standard pre-defined deployment configuration provided by AWS CodeDeploy for ECS.

Anahtar Kavram

AWS CodeDeploy deployment configurations for ECS Blue/Green deployments control how traffic is shifted from the old task set to the new task set, allowing canary testing with built-in validation periods.
Soru 64Soru →

A developer is deploying a new version of a critical web application to AWS Elastic Beanstalk. The deployment must satisfy the following constraints:

- The application must maintain 100%100\% of its serving capacity throughout the deployment process to handle high user traffic without performance degradation.
- In the event of a deployment failure, the application must support an immediate rollback to the previous version without requiring a rolling update of the older version.
- The development team has approved a temporary increase in resource capacity to allow up to twice the normal instance count during the deployment.

Which deployment strategy will meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Immutable

Cevap

The Immutable deployment strategy satisfies all the constraints by maintaining full capacity during deployment, supporting immediate rollback, and utilizing a temporary doubling of instance resources.
The Immutable deployment strategy deploys the new version to a separate, temporary Auto Scaling group alongside the existing one. This preserves 100%100\% capacity throughout the deployment. If health checks fail, the rollback is immediate because Elastic Beanstalk simply terminates the new Auto Scaling group without affecting the original instances. This strategy temporarily doubles the resource count, which is acceptable under the approved budget increase.

Adım Adım Çözüm

1
Analyze the capacity requirement.
The application must maintain 100%100\% capacity during the deployment. This rules out All-at-once (causes downtime) and Rolling (reduces capacity during deployment).
To identify strategies that can sustain the required traffic load without performance degradation.
2
Evaluate the rollback and budget constraints.
The rollback must be immediate and clean. Additionally, a temporary doubling of instance capacity is allowed. This matches the Immutable strategy, which deploys to a temporary Auto Scaling group and can be quickly terminated upon failure. Rolling with additional batch is ruled out because its rollback requires a slow rolling deployment of the older version.
To determine which of the remaining strategies satisfies both the recovery time objective and the resource availability parameters.

Anahtar Kavram

Understanding the trade-offs of AWS Elastic Beanstalk deployment strategies, specifically regarding capacity preservation, rollback mechanism, and temporary cost overhead.
Tahmini Süre:1m 30s
Soru 65Soru →

A developer is configuring a blue/green deployment for a containerized application on Amazon ECS using AWS CodeDeploy. The deployment configuration utilizes an Application Load Balancer with two target groups and a test listener. The developer wants to run automated integration tests against the replacement task set via the test listener to validate the new version of the application before shifting any production traffic.

Which AppSpec lifecycle hook should the developer use to run these integration tests?

Cevabı ve açıklamayı göster

Cevap: AfterAllowTestTraffic

Cevap

AfterAllowTestTraffic
The correct answer is the hook named AfterAllowTestTraffic. During an ECS blue/green deployment, AWS CodeDeploy executes hooks in a specific order: BeforeInstall, AfterInstall, AfterAllowTestTraffic, BeforeAllowTraffic, and AfterAllowTraffic. The test listener begins routing traffic to the replacement task set just before AfterAllowTestTraffic runs. This is the only point where the application is reachable via the test listener for validation tests before the production listener is updated to point to the replacement task set.

Adım Adım Çözüm

1
Analyze the deployment architecture and requirements.
The target is Amazon ECS using AWS CodeDeploy for blue/green deployment. The requirement is to run automated integration tests against the replacement (new) task set using the test listener before shifting production traffic.
Understanding the target platform and specific validation workflow constraints is essential for selecting the correct lifecycle hook.
2
Map the sequence of AWS CodeDeploy ECS lifecycle hooks.
The ECS lifecycle hooks run in the following order: BeforeInstall -> AfterInstall -> AfterAllowTestTraffic -> BeforeAllowTraffic -> AfterAllowTraffic. The test listener starts routing traffic to the replacement tasks just before the AfterAllowTestTraffic hook runs.
Identifying the execution order of ECS hooks allows us to determine when the replacement tasks are reachable via the test listener.
3
Select the hook that matches the requirement of using the test listener for validation.
The AfterAllowTestTraffic hook is executed after the test listener begins routing traffic to the replacement task set. This allows running tests against the test listener endpoint.
Running tests at any other stage would fail because the replacement task set would not yet be reachable via the test listener.

Anahtar Kavram

AWS CodeDeploy ECS Blue/Green Lifecycle Hooks
Soru 66Soru →

An organization runs a critical web application on a fleet of Amazon EC2 instances managed by an Auto Scaling group. The developer needs to configure a deployment strategy for application updates that guarantees the application maintains 100% of its capacity throughout the deployment process. Additionally, if the new version fails health checks, the system must support the fastest possible rollback to the previous version with minimal operational overhead. The organization accepts the temporary additional cost of provisioning duplicate resources during the deployment.

Which two deployment strategies meet these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Blue/green deployment; Immutable deployment

Cevap

Blue/green deployment and Immutable deployment
Blue/green deployment and immutable deployment are the correct choices. Both strategies deploy the new version on new, separate resources while the original resources remain fully functional, ensuring 100% capacity is maintained. If a failure occurs, rollback is nearly instantaneous: traffic is directed back to the original instances (for blue/green) or the new resources are deleted (for immutable), requiring no redeployment overhead.

Adım Adım Çözüm

1
Analyze capacity requirements.
The requirement specifies maintaining 100% capacity during deployment. This eliminates strategies that take existing instances offline, such as rolling deployment.
To ensure no performance degradation or downtime during the deployment.
2
Analyze rollback requirements.
The requirement specifies the fastest possible rollback. This eliminates strategies that require redeploying the old version in place, such as rolling with additional batch.
To minimize the mean time to recovery (MTTR) if a faulty version is deployed.
3
Evaluate remaining options against resource costs.
Both blue/green and immutable deployments deploy to new resources, maintaining 100% capacity of the old version and allowing instantaneous rollback (by switching DNS/routing or terminating new resources). Both meet the budget constraint because the organization accepts temporary duplicate resource costs.
To select the strategies that align with the cost profile and technical requirements.

Anahtar Kavram

Deployment strategies present different trade-offs among deployment time, capacity during deployment, rollback speed, and resource costs.
Soru 67Soru →

A development team needs to deploy an update to an Amazon ECS service running on an EC2-backed cluster. The service currently runs 4 tasks. Due to strict budget limits, the cluster has no additional EC2 instance capacity to run extra tasks during the deployment. However, the service must maintain at least 50% of its capacity at all times to handle the baseline request volume. Which ECS service deployment configuration should the developer specify to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Set the minimum healthy percent to 50% and the maximum percent to 100%.

Cevap

Set the minimum healthy percent to 50% and the maximum percent to 100%.
The correct option sets the minimum healthy percent to 50% and the maximum percent to 100%. This ensures that at least 2 tasks remain running at all times to handle baseline traffic. Because the maximum percent is 100%, ECS will not attempt to exceed 4 tasks at any point, meaning it will first terminate 2 old tasks to free up space on the existing EC2 hosts before launching 2 new tasks.

Adım Adım Çözüm

1
Analyze the service configuration and constraints.
Current tasks = 4. Target minimum capacity = 50% (2 tasks). Additional EC2 capacity = 0.
To ensure no extra EC2 capacity is used, the maximum percent must not exceed 100%.
2
Evaluate the rolling update deployment parameter mathematical constraints.
Maximum percent of 100% means the service cannot exceed 4 concurrent tasks. Minimum healthy percent of 50% means at least 2 tasks must remain active.
This forces ECS to stop 2 tasks first, freeing up slot capacity on existing instances, and then start 2 new tasks.
3
Select the matching configuration option.
Minimum healthy percent = 50%, Maximum percent = 100%.
This is the only configuration that maintains the baseline service capacity without requiring extra EC2 instances.

Anahtar Kavram

Amazon ECS Rolling Update deployment parameters (minimumHealthyPercent and maximumPercent) control the task lifecycle and capacity requirements during a deployment.
Tahmini Süre:1m 30s
Soru 68Soru →

A developer is updating a critical serverless application and needs to configure traffic shifting for a new version of an AWS Lambda function using AWS CodeDeploy. The deployment must meet the following requirements:

* Route exactly 10%10\% of traffic to the new version in the first increment.
* Allow at least 1010 minutes of monitoring for errors before shifting any additional traffic or completing the deployment.

Which two AWS CodeDeploy deployment configurations should the developer select to meet these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: CodeDeployDefault.LambdaCanary10Percent10Minutes; CodeDeployDefault.LambdaLinear10PercentEvery10Minutes

Cevap

The correct configurations are CodeDeployDefault.LambdaCanary10Percent10Minutes and CodeDeployDefault.LambdaLinear10PercentEvery10Minutes.
The configurations CodeDeployDefault.LambdaCanary10Percent10Minutes and CodeDeployDefault.LambdaLinear10PercentEvery10Minutes both satisfy the requirements. The canary configuration shifts 10%10\% of the traffic to the new version initially and waits 1010 minutes before shifting the remaining 90%90\%. The linear configuration shifts 10%10\% initially and waits 1010 minutes before shifting the next 10%10\% increment, which allows the required 1010 minutes of monitoring in both cases.

Adım Adım Çözüm

1
Analyze the requirement for initial traffic allocation.
The configuration must shift exactly 10%10\% of the traffic in the first increment. This rules out CodeDeployDefault.LambdaAllAtOnce, which shifts 100%100\% immediately.
Identifying the initial increment size helps narrow down the candidates to Canary 10%10\% and Linear 10%10\% configurations.
2
Evaluate the monitoring window constraint of at least 1010 minutes before shifting more traffic.
CodeDeployDefault.LambdaCanary10Percent5Minutes shifts the remaining traffic after 55 minutes, and CodeDeployDefault.LambdaLinear10PercentEvery1Minute shifts more traffic after 11 minute. Both fail the 1010-minute threshold.
Eliminating configurations that shift traffic too quickly ensures the deployment meets the safety window constraint.
3
Confirm the configurations that meet both constraints.
CodeDeployDefault.LambdaCanary10Percent10Minutes (shifts 10%10\% and waits 1010 minutes) and CodeDeployDefault.LambdaLinear10PercentEvery10Minutes (shifts 10%10\% and waits 1010 minutes before each subsequent shift) both satisfy the requirements.
Both configurations guarantee a 10%10\% initial traffic split and a minimum of 1010 minutes of evaluation time before further traffic modification.

Anahtar Kavram

AWS CodeDeploy deployment configurations for AWS Lambda functions specify how traffic is shifted between the original and new versions. Canary configurations shift a specified percentage in one increment and then shift the rest after a delay. Linear configurations shift traffic in equal increments at regular intervals.
Tahmini Süre:1m 30s
Soru 69Soru →

A developer is planning the deployment of a new version of a critical web application hosted on AWS Elastic Beanstalk. The application runs on a fleet of Amazon EC2 instances managed by an Auto Scaling group behind an Application Load Balancer. The deployment must satisfy the following constraints:

* The update must be rolled out with zero downtime.
* The application must maintain 100%100\% of its instance capacity to handle the current traffic load at all times during the deployment.
* In the event of a deployment failure, the application must support an immediate rollback to the previous version without requiring a full redeployment of the original code.

Which two deployment strategies meet these requirements? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Blue/Green deployment; Immutable deployment

Cevap

Blue/Green deployment and Immutable deployment
Blue/Green deployment and Immutable deployment satisfy all requirements. Blue/Green deployment provisions a separate environment with the new version and performs a DNS CNAME swap, keeping both environments at 100%100\% capacity and allowing an instant swap back in case of failure. Immutable deployment creates a temporary Auto Scaling group with the new version alongside the existing one, maintaining 100%100\% capacity, and immediately rolls back by terminating the new Auto Scaling group if the deployment fails.

Adım Adım Çözüm

1
Analyze the capacity requirement.
Since the application must maintain 100%100\% of its instance capacity during the deployment, strategies that take existing instances out of service (like Rolling and All at once) are disqualified.
To ensure there is no performance degradation under high load.
2
Analyze the rollback requirement.
The rollback must be immediate and not require a full redeployment. This disqualifies Rolling with additional batch deployment, where rollback requires redeploying the old version onto updated instances.
To minimize the duration of service issues if the new version is buggy.
3
Evaluate the remaining options.
Blue/Green deployment (via CNAME swap) and Immutable deployment both run a full set of new instances alongside the old ones (maintaining 100%100\% capacity) and support immediate rollback (by swapping CNAMEs back or terminating the temporary Auto Scaling group, respectively).
Both strategies satisfy all the constraints in the scenario.

Anahtar Kavram

AWS Elastic Beanstalk deployment strategies trade-offs including capacity, downtime, and rollback mechanisms.
Soru 70Soru →

A developer is releasing an update to a production REST API managed by Amazon API Gateway. The update includes changes to both the API Gateway resource structure and the backend integrations. To minimize risk, the developer wants to route 15%15\% of the API traffic to the new version while the remaining 85%85\% is handled by the stable production version. The strategy must support immediate rollback to the stable version without modifying client configurations or deploying new API stages. Which approach should the developer use to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure a canary release on the existing API Gateway deployment stage and set the canary traffic percentage to 15%15\%.

Cevap

Configure a canary release on the existing API Gateway deployment stage and set the canary traffic percentage to 15%15\%.
Configuring a canary release on the existing API Gateway stage is the only option that keeps the endpoint URL unchanged for clients, avoids creating new stages, and allows immediate rollback by deleting the canary release.

Adım Adım Çözüm

1
Analyze the deployment constraints: 15%15\% traffic routing, 85%85\% remaining on stable, immediate rollback capability, no client configuration changes, and no creation of new API stages.
Identify that the deployment must take place within the existing API Gateway stage and support built-in traffic shifting.
Creating new stages or changing DNS/client endpoints is prohibited by the scenario requirements.
2
Evaluate the capabilities of Amazon API Gateway deployment stages.
Determine that API Gateway supports configuring a Canary release directly on a stage, allowing a designated percentage of traffic (e.g., 15%15\%) to be sent to a new deployment.
This configuration keeps the stage endpoint URL identical for clients and allows immediate promotion or deletion of the canary to rollback.
3
Compare the correct API Gateway canary configuration with other alternatives.
Confirm that Route 53, CodeDeploy, and Application Load Balancer solutions either require new stages or are not supported natively for shifting API Gateway stage configuration traffic.
Eliminating options that violate the no-new-stage constraint ensures the selection of the correct option.

Anahtar Kavram

API Gateway Canary Deployments
Soru 71Soru →

A developer is configuring an in-place deployment using AWS CodeDeploy for an application running on a fleet of 88 Amazon EC2 instances behind an Application Load Balancer. The application must maintain at least 75%75\% of its serving capacity throughout the deployment process. Which TWO of the following CodeDeploy deployment configurations can the developer use to meet this requirement? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Use the predefined CodeDeployDefault.OneAtATime deployment configuration.; Create a custom deployment configuration with the minimum healthy hosts set to a percentage of 75%75\%.

Cevap

To maintain at least 75%75\% capacity of the 88-instance fleet during deployment, the developer can either use the predefined OneAtATime configuration or create a custom configuration with the minimum healthy hosts set to 75%75\%.
To maintain at least 75%75\% capacity of an 88-instance fleet, CodeDeploy must keep at least 66 instances healthy at all times (8×0.75=68 \times 0.75 = 6). The predefined configuration that deploys to one instance at a time ensures that 77 out of 88 instances (87.5%87.5\%) remain healthy during the deployment, which satisfies the 75%75\% threshold. Alternatively, creating a custom deployment configuration with the minimum healthy hosts explicitly set to a percentage of 75%75\% directly guarantees that at least 66 instances remain online and healthy.

Adım Adım Çözüm

1
Calculate the minimum number of healthy instances required during deployment.
88 instances ×0.75=6\times 0.75 = 6 healthy instances.
The scenario requires maintaining at least 75%75\% capacity of the fleet.
2
Evaluate the predefined CodeDeploy deployment configurations against the calculated minimum capacity.
The predefined OneAtATime configuration leaves 77 instances healthy (87.5%87.5\%), which is greater than or equal to 75%75\%. The HalfAtATime configuration leaves 44 instances healthy (50%50\%), and AllAtOnce leaves 00 healthy (0%0\%). Both are less than 75%75\% and are therefore incorrect.
To identify which predefined configuration satisfies the capacity constraint.
3
Evaluate custom deployment configurations to enforce the threshold.
A custom deployment configuration with minimum healthy hosts set to 75%75\% directly guarantees 66 healthy instances remain online, whereas a minimum healthy host configuration set to 25%25\% allows capacity to drop to 22 instances, failing the requirement.
To select the correct custom configuration option.

Anahtar Kavram

CodeDeploy Deployment Configurations
Soru 72Soru →

An organization is deploying updates to a high-traffic web application hosted on AWS Elastic Beanstalk. The application is highly sensitive to performance issues, so the deployment process must maintain 100%100\% of the current instance capacity at all times. Additionally, if the new version fails health checks, the deployment must support an immediate rollback that does not alter or disrupt the active instances in the original environment. Which two Elastic Beanstalk deployment policies will meet these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Immutable; Traffic Splitting

Cevap

The Immutable and Traffic Splitting deployment policies should be selected.
The Immutable and Traffic Splitting policies both satisfy the constraints. The Immutable policy creates a temporary Auto Scaling group to launch the new version alongside the original one. Once health checks pass, traffic is shifted. Traffic Splitting routes a configured percentage of traffic to a new temporary Auto Scaling group for evaluation. In both cases, the original instances remain untouched, maintaining 100%100\% capacity and enabling instant rollback by simply deleting the temporary resources.

Adım Adım Çözüm

1
Analyze capacity requirements.
The strategy must maintain 100%100\% capacity during deployment, which rules out All at once and Rolling strategies.
Maintaining full capacity requires launching new instances before terminating old ones.
2
Analyze rollback constraints.
The rollback must be immediate and must not alter or affect the running production instances if the update fails. This rules out Rolling with additional batch, which updates active instances and requires a slow rolling rollback.
To prevent disruption, the original instances must remain untouched until the new version is verified.
3
Select the matching Elastic Beanstalk policies.
Immutable and Traffic Splitting satisfy both constraints as they launch new instances in a temporary group and only transition traffic once verified.
Both policies keep the original instances completely intact during evaluation and allow instant cleanup/rollback upon failure.

Anahtar Kavram

AWS Elastic Beanstalk deployment policies and their impact on environment capacity, duration, and rollback mechanisms.
Soru 73Soru →

A developer is configuring an AWS CodeDeploy Blue/Green deployment for a critical web application. The application runs on Amazon EC2 instances managed by an Auto Scaling group behind an Application Load Balancer. The deployment must satisfy the following constraints:

- If any issues are detected after shifting traffic to the new (Green) fleet, the application must be rolled back to the original (Blue) fleet within a 11-hour window.
- The rollback must be nearly instantaneous, avoiding the time required to provision new EC2 instances or initialize the application.
- To control costs, all resources from the original fleet must be automatically terminated after the 11-hour window if no issues are detected.

Which configuration settings in the CodeDeploy deployment group will meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure the deployment group to redirect traffic immediately, set the action on the original instances to keep them running, and specify a rerun transition wait time of 11 hour before termination.

Cevap

Configure the deployment group to redirect traffic immediately, set the action on the original instances to keep them running, and specify a rerun transition wait time of 11 hour before termination.
The correct configuration is to configure the deployment group to redirect traffic immediately, keep the original instances running, and specify a wait time of 11 hour. In a CodeDeploy Blue/Green deployment, keeping the original (Blue) instances running inside the original Auto Scaling group allows CodeDeploy to perform a near-instantaneous rollback if an issue is detected. If the validation timer of 11 hour expires without any rollback being triggered, CodeDeploy automatically terminates the original instances and Auto Scaling group, ensuring that costs are controlled.

Adım Adım Çözüm

1
Analyze the rollback requirement.
Since the rollback must be nearly instantaneous, the original (Blue) instances must remain running and active in their target group during the testing period.
If the instances are terminated, rolling back requires provisioning new EC2 instances, which takes several minutes and violates the time constraint.
2
Analyze the cost optimization requirement.
The original instances should not run indefinitely; they must be automatically terminated after the validation window.
This is achieved by specifying a wait time (e.g., 11 hour) in CodeDeploy's deployment configuration settings for original instances.
3
Select the correct CodeDeploy configuration option.
Configure CodeDeploy to redirect traffic immediately, keep the original fleet running, and set the wait time to 11 hour.
This satisfies all constraints by preserving the instances for fast rollback while ensuring automatic cleanup after 11 hour.

Anahtar Kavram

AWS CodeDeploy Blue/Green Deployment Instance Termination Lifecycle
Soru 74Soru →

A developer is configuring a CI/CD pipeline for a microservice deployed on Amazon ECS. The company requires a deployment strategy that minimizes the blast radius by shifting traffic to the new version of the application in multiple stages (either in a single initial test phase followed by a complete cutover, or in periodic increments). The deployment must also support automatic rollbacks if any CloudWatch alarms are triggered. Which two AWS CodeDeploy predefined deployment configurations can the developer use to meet these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: CodeDeployDefault.ECSCanary10Percent5Minutes; CodeDeployDefault.ECSLinear10PercentEvery1Minutes

Cevap

CodeDeployDefault.ECSCanary10Percent5Minutes and CodeDeployDefault.ECSLinear10PercentEvery1Minutes
The configurations CodeDeployDefault.ECSCanary10Percent5Minutes and CodeDeployDefault.ECSLinear10PercentEvery1Minutes are correct because they are predefined deployment configurations for Amazon ECS. The Canary configuration routes 10% of traffic to the green task set and waits 5 minutes before routing the rest, while the Linear configuration shifts traffic in equal increments of 10% every minute. Both meet the requirement of gradual traffic shifting and support automatic rollback via CloudWatch alarms.

Adım Adım Çözüm

1
Filter deployment configurations by targeted service.
Identify that the target service is Amazon ECS, which eliminates Lambda-specific configurations.
AWS CodeDeploy separates predefined configurations for ECS, Lambda, and EC2/On-Premises; attempting to cross-assign them results in errors.
2
Evaluate the traffic routing requirement.
Identify configurations that support gradual traffic shifting (Canary or Linear) rather than an immediate cutover.
The requirement asks for shifting traffic in multiple stages or periodic increments to minimize blast radius.
3
Select matching predefined configurations.
Choose the configurations matching ECS canary and linear strategies.
Both configurations allow testing with a subset of traffic before full cutover and support automatic rollback via CloudWatch alarms.

Anahtar Kavram

AWS CodeDeploy deployment configurations for Amazon ECS support Canary and Linear traffic shifting to control blast radius and facilitate automatic rollbacks.
Tahmini Süre:1m 30s
Soru 75Soru →

A developer is planning to deploy a new version of an application on AWS Elastic Beanstalk. The application is currently running in a single production environment containing 44 Amazon EC2 instances behind an Application Load Balancer. The deployment must meet the following constraints:
- The environment must maintain 100%100\% of its processing capacity (44 active instances) during the deployment process.
- To control cost, the developer must not create a separate, duplicate Elastic Beanstalk environment or perform a DNS swap.
- The rollback process must be fully automated in the event that the new version fails application health checks.

Which Elastic Beanstalk deployment policy should the developer select?

Cevabı ve açıklamayı göster

Cevap: Immutable

Cevap

The Immutable deployment policy should be selected because it maintains 100%100\% capacity by deploying the new version to a temporary Auto Scaling group, automatically rolls back if health checks fail, and operates within a single Elastic Beanstalk environment.
The Immutable deployment policy satisfies all constraints. It maintains 100%100\% capacity by launching a temporary Auto Scaling group with the new version alongside the original instances. If the new version fails health checks, Elastic Beanstalk automatically deletes the temporary Auto Scaling group, rolling back the deployment. Additionally, it avoids the overhead of managing a separate Elastic Beanstalk environment.

Adım Adım Çözüm

1
Analyze the capacity requirement during deployment.
The environment must maintain 100%100\% of its processing capacity (44 active instances) at all times.
This rules out the standard Rolling deployment policy, which takes some instances offline to update them, reducing active capacity.
2
Analyze the rollback requirement.
The deployment must automatically roll back to the previous version without manual intervention if health checks fail.
This rules out Rolling with additional batch, which requires a manual rollback deployment if the new version is unhealthy.
3
Analyze the environment management and cost constraint.
The developer must avoid creating a separate environment or performing a DNS swap.
This rules out the Blue/Green environment swap strategy, leaving the Immutable policy as the only one satisfying all constraints.

Anahtar Kavram

AWS Elastic Beanstalk deployment policies and their trade-offs regarding capacity, rollback behavior, and environment overhead.
Soru 76Soru →

A developer needs to deploy a new version of a critical web application. The deployment must satisfy the following constraints:
- The application must maintain 100%100\% of its serving capacity throughout the deployment.
- The deployment must have zero downtime.
- The deployment must not modify the existing production instances until the new version is fully verified.
- Rollbacks must be fast and have minimal impact on the active production environment if the new version fails verification.

Which two deployment strategies will satisfy these requirements? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Blue/Green deployment; Immutable deployment

Cevap

The correct strategies are Blue/Green deployment and Immutable deployment.
The correct strategies are Blue/Green deployment and Immutable deployment. Both strategies deploy the new version of the application to new resources that are separate from the active production environment. This ensures that the active environment is not modified during the deployment, 100%100\% capacity is maintained using the old version, and rollbacks are fast and simple (either by swapping DNS/traffic back or by terminating the temporary instances) if the verification fails.

Adım Adım Çözüm

1
Analyze the capacity requirement
Strategies like Rolling or All-at-once, which temporarily take existing instances out of service, are eliminated because they reduce capacity below 100%100\%.
The requirement states that 100%100\% capacity must be maintained at all times.
2
Analyze the requirement to not modify existing instances until verified
Strategies like Rolling with additional batch are eliminated because they perform in-place updates on existing production instances during the rollout.
The system must keep the existing production environment untouched during the verification phase of the new version.
3
Evaluate Blue/Green and Immutable strategies
Both Blue/Green and Immutable deployments provision new resources separately from the active production fleet, keep the active environment intact until fully verified, support zero downtime, and can roll back instantly by redirecting traffic or terminating the new temporary resource group.
These strategies align perfectly with the need for zero downtime, full capacity, isolated verification, and rapid rollback.

Anahtar Kavram

Deployment strategies vary in how they handle capacity, resource overhead, in-place modifications, and rollback speed. Blue/Green and Immutable deployments prevent modification of existing production resources during validation, while Rolling and All-at-once modify them in-place.
Tahmini Süre:2m 0s
Soru 77Soru →

An organization hosts a web application on an AWS Elastic Beanstalk environment. The operations team needs to deploy a minor software update. Due to strict AWS account limits, the environment cannot launch any additional Amazon EC2 instances during the deployment. The application must remain online and accessible to users, but it can tolerate running at a minimum of 50%50\% of its total instance capacity during the deployment. Which Elastic Beanstalk deployment policy should the developer configure to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Rolling

Cevap

Rolling
The Rolling deployment strategy updates the application in batches on the existing instances. This ensures that no new EC2 instances are provisioned during the process, adhering to the strict service limits. Because it updates one batch at a time, the application remains online, satisfying the availability requirement while running at the tolerated reduced capacity.

Adım Adım Çözüm

1
Evaluate the capacity constraints and compute the allowed additional resources.
Zero new Amazon EC2 instances can be launched due to strict AWS account limits.
This rules out deployment strategies that require provisioning new instances, such as Immutable or Rolling with additional batch.
2
Analyze the availability requirement for the web application.
The application must remain online and accessible to users.
This rules out the All at once deployment strategy, which takes all instances out of service simultaneously.
3
Evaluate the remaining candidate strategies against the performance threshold.
The Rolling policy is selected because it updates instances in batches without creating new instances, while maintaining application availability at a reduced capacity of at least 50%50\%.
Rolling updates satisfy the zero-new-instance limit and the online requirement by using existing instances in batches.

Anahtar Kavram

AWS Elastic Beanstalk deployment policies and their resource/capacity trade-offs
Tahmini Süre:1m 30s
Soru 78Soru →

A developer is configuring a rolling update deployment for an Amazon ECS service. The service has a desired task count of 12. To ensure high availability and prevent performance degradation under peak load, the service must maintain 100% of its desired capacity at all times during the deployment. Furthermore, due to CPU and memory constraints on the underlying container instances, the deployment can run at most 3 additional tasks concurrently. Which parameters for minimum healthy percent and maximum percent should the developer configure for the ECS service?

Cevabı ve açıklamayı göster

Cevap: Minimum healthy percent of 100% and maximum percent of 125%

Cevap

Minimum healthy percent of 100% and maximum percent of 125%
The correct configuration is to set the minimum healthy percent to 100% and the maximum percent to 125%. The minimum healthy percent of 100% ensures that the ECS service always has at least 12 healthy tasks running (100% of the desired count of 12). The maximum percent of 125% allows the service to temporarily scale up to 15 tasks (125% of 12) during the deployment, representing the 3 additional tasks permitted by the resource constraints.

Adım Adım Çözüm

1
Calculate the minimum number of running tasks required based on the capacity constraint.
The minimum number of running tasks must be 12 (100% of the desired count of 12 tasks). Therefore, the minimum healthy percent is 100%.
The requirement states that the service must maintain 100% of its desired capacity at all times during the deployment.
2
Calculate the maximum number of running tasks allowed based on container instance resources.
The maximum number of running tasks allowed is 15 tasks (12 desired + 3 additional tasks).
The requirement states that the deployment can run at most 3 additional tasks concurrently.
3
Convert the maximum task count into a percentage of the desired count.
Maximum percent = (15 / 12) * 100 = 125%.
ECS service definitions express the maximum task limit during deployment as a percentage of the desired task count.

Anahtar Kavram

Amazon ECS rolling update deployment configuration parameters (minimumHealthyPercent and maximumPercent)
Soru 79Soru →

A developer is designing a deployment pipeline for a critical microservice on AWS. The deployment process must ensure zero downtime, allow testing of the new application version with a small fraction of production traffic before shifting all traffic, and support automatic rollback if CloudWatch alarms detect errors.

Which two deployment strategies or configurations will satisfy these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: An AWS CodeDeploy Canary deployment for an AWS Lambda function; An AWS CodeDeploy Linear deployment for an Amazon ECS service

Cevap

The deployment configurations that satisfy the requirements are the AWS CodeDeploy Canary deployment for an AWS Lambda function and the AWS CodeDeploy Linear deployment for an Amazon ECS service.
The correct strategies are the AWS CodeDeploy Canary deployment for an AWS Lambda function and the AWS CodeDeploy Linear deployment for an Amazon ECS service. Both configurations leverage traffic shifting (either at the Lambda alias level or via an Application Load Balancer target group for ECS) to route a small percentage of production traffic to the new version. Additionally, CodeDeploy monitors CloudWatch alarms during the deployment and can trigger an automatic, near-instantaneous rollback if errors are detected.

Adım Adım Çözüm

1
Analyze the requirement for gradual traffic shifting to test the new version with a small fraction of production traffic.
Identify that AWS CodeDeploy Canary and Linear configurations support routing a small percentage of traffic (e.g., 10%) initially.
This isolates the test traffic and minimizes blast radius.
2
Evaluate the rollback requirements under failure conditions.
Identify that AWS CodeDeploy integrates with CloudWatch alarms to monitor the deployment and automatically roll back if errors occur.
This satisfies the automatic rollback requirement without manual intervention.
3
Verify if the remaining options satisfy the constraints.
Eliminate Elastic Beanstalk All-at-Once (downtime), ECS Rolling Update (no dedicated canary traffic shifting or automated alarm integration), and Elastic Beanstalk Rolling (no fine-grained traffic routing and automated rollback).
These strategies fail to meet either the zero-downtime, traffic-routing, or automatic rollback constraints.

Anahtar Kavram

Gradual traffic shifting and automated rollback using AWS CodeDeploy configurations for Lambda and ECS.
Tahmini Süre:2m 0s
Soru 80Soru →

A developer is updating a critical AWS Lambda function using AWS CodeDeploy. The deployment must route 10%10\% of the production traffic to the new version of the function first. The deployment must then automatically shift the remaining 90%90\% of the traffic to the new version after exactly 1515 minutes, provided that no CloudWatch alarms are triggered during this window.

Which AWS CodeDeploy deployment configuration should the developer choose to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: CodeDeployDefault.LambdaCanary10Percent15Minutes

Cevap

CodeDeployDefault.LambdaCanary10Percent15Minutes
The correct configuration is the canary deployment option that specifies a 10%10\% initial traffic shift followed by a 1515-minute monitoring interval before the remaining 90%90\% is shifted. This matches the configuration named CodeDeployDefault.LambdaCanary10Percent15Minutes.

Adım Adım Çözüm

1
Identify the deployment strategy type from the requirements.
The requirements describe a canary deployment strategy because traffic is shifted in two stages: an initial minor shift (10%10\%) and a final complete shift (90%90\%) after a specific wait period (1515 minutes).
Determining the correct class of deployment configuration narrows down the options between canary and linear.
2
Extract the specific percentage and time parameters.
The initial percentage is 10%10\%, and the wait time is 1515 minutes.
These parameters map directly to the names of the predefined deployment configurations in CodeDeploy.
3
Select the built-in configuration that matches these parameters.
The built-in configuration that routes 10%10\% first and waits 1515 minutes is CodeDeployDefault.LambdaCanary10Percent15Minutes.
This configuration satisfies all the criteria of the scenario.

Anahtar Kavram

AWS CodeDeploy deployment configurations for AWS Lambda functions
Tahmini Süre:1m 30s
ÖncekiSayfa 4 / 5Sonraki
Deployment Strategies Alıştırma Soruları — AWS Certified Developer - Associate — Sayfa 4 | Examkin