A company has an Amazon EC2 instance that has high CPU utilization. The EC2 instance is a t3.large instance and is running a test web application. The company discovers that the web application…

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
  2% (1)
• B
  5% (2)
• C
  90% (37)
• D
  2% (1)

Explanation

Stopping the instance first is the required procedure for changing an EC2 instance type. AWS only allows instance type changes when the instance is in a stopped state - you stop it, modify the instance type attribute, then start it again, and the instance launches on new underlying hardware matching the selected family.

Why the distractors are wrong:

• A - VM Import/Export is for migrating workloads into AWS from on-premises or other clouds, not for changing instance types within AWS.
• B - Hibernation preserves RAM state to an EBS volume for faster resume, but it does not enable live instance type changes; you still cannot change the type without stopping the instance (and not all instance types support hibernation anyway).
• D - AWS does not allow changing the instance type of a running instance; the option is simply grayed out in the console and blocked via API until the instance is stopped.

Memory tip: Think of changing an instance type like swapping a CPU in a physical server - you have to power it off first. "Stop → Change → Start" is the three-step mantra for any EC2 instance type change.

No community discussion yet for this question.