A company's Amazon EC2 instance with high CPU utilization is a t3.large instance running a test web app. The company determines the app would run better on a compute-optimized large instance. What…

Question

Options

• AMigrate the EC2 instance to a compute optimized instance by using AWS VM Import/Export.
• BEnable hibernation on the EC2 instance. Change the instance type to a compute optimized
• CStop the EC2 instance. Change the instance type to a compute optimized instance. Start the EC2
• DChange the instance type to a compute optimized instance while the EC2 instance is running.

• A
  18% (9)
• B
  4% (2)
• C
  70% (35)
• D
  8% (4)

Explanation

As described in the AWS Cloud Operations and EC2 Management documentation, changing an instance type (e.g., from T3 to C5) requires that the instance be stopped first. Once stopped, the engineer can modify the instance type through the AWS Management Console, CLI, or API, then start the instance again to apply changes. This process preserves the root volume, networking configuration, and data, making it an operationally safe and efficient way to upgrade to a different instance family. Changing the instance type while running (Option D) is unsupported. VM Import/Export (Option A) is for external VM migration. Hibernation (Option B) does not apply to type changes. Thus, Option C is correct -- stopping the instance, changing its type, and restarting it meets AWS

No community discussion yet for this question.