SOA-C02 · Question #609
A SysOps administrator supports a publicly accessible web application that runs on Amazon EC2 instances. The SysOps administrator wants to migrate the EC2 instances to AWS Graviton2- based EC2…
The correct answer is B. The AMI that was used in the launch configuration is not compatible with Arm-based instances. Option B is correct because AWS Graviton2 instances use the Arm (aarch64) architecture, which requires an AMI specifically built for Arm - an x86_64 AMI (the default for most EC2 workloads) is incompatible, causing the "requested configuration is currently not supported" error…
Question
A SysOps administrator supports a publicly accessible web application that runs on Amazon EC2 instances. The SysOps administrator wants to migrate the EC2 instances to AWS Graviton2- based EC2 instances. In a testing account, the SysOps administrator creates a replica stack that consists of an Amazon EC2 Auto Scaling group and an Amazon RDS database. The SysOps administrator creates a new launch configuration that uses the new Graviton2-based instance with the latest version of the application's Amazon Machine Image (AMI). The SysOps administrator attempts to create the test application. The test application fails to launch and produces the following error message: "The requested configuration is currently not supported." What is the cause of the failure to launch the test application?
Options
- AThe key pair that was used during the instance launch has been deleted.
- BThe AMI that was used in the launch configuration is not compatible with Arm-based instances.
- CThe selected instance type is not available in the selected Availability Zone.
- DThe launch configuration is configured with improper block device settings.
How the community answered
(26 responses)- A8% (2)
- B85% (22)
- C4% (1)
- D4% (1)
Explanation
Option B is correct because AWS Graviton2 instances use the Arm (aarch64) architecture, which requires an AMI specifically built for Arm - an x86_64 AMI (the default for most EC2 workloads) is incompatible, causing the "requested configuration is currently not supported" error. Option A is wrong because a deleted key pair would produce an authentication/access error, not a configuration support error. Option C is wrong because instance type availability issues produce a different error ("insufficient capacity" or "not available in this zone"), not a configuration support message. Option D is wrong because block device misconfigurations typically cause launch failures with storage-related errors, not architecture compatibility errors.
Memory tip: Think "Graviton = ARM = different architecture = need a matching AMI." Just like you can't run an iOS app on Android, you can't run an x86 AMI on an Arm instance - the AMI must match the CPU architecture.
Topics
Community Discussion
No community discussion yet for this question.