A user working in the Amazon EC2 console increased the size of an Amazon Elastic Block Store (Amazon EBS) volume attached to an Amazon EC2 Windows instance. The change is not reflected in the file…

Question

Options

• AExtend the file system with operating system-level tools to use the new storage capacity.
• BReattach the EBS volume to the EC2 instance.
• CReboot the EC2 instance that is attached to the EBS volume.
• DTake a snapshot of the EBS volume. Replace the original volume with a volume that is created

• A
  79% (22)
• B
  4% (1)
• C
  11% (3)
• D
  7% (2)

Explanation

EBS Volume Expansion Explanation

Extending an EBS volume in the AWS console only increases the underlying block storage capacity - it does not automatically update the file system partition that the OS uses. On a Windows instance, a CloudOps engineer must use Disk Management or the diskpart command-line tool to extend the volume/partition so the OS can recognize and use the additional space.

Why the distractors are wrong:

• B (Reattach the volume): Detaching and reattaching the volume does nothing to update the file system partition; the OS will still see the original size.
• C (Reboot the instance): A reboot does not trigger file system extension; the partition table remains unchanged after restart.
• D (Snapshot and replace): Creating a snapshot and replacing the volume is unnecessary, overly complex, and would still require file system extension afterward anyway.

Memory Tip: Think of it as a two-step process - AWS expands the "container" (the EBS volume), but you must expand the "shelf inside" (the file system/partition) using OS tools. The AWS console only handles the hardware layer; the OS handles the logical layer. Remember: "AWS gives you the space, you claim it."

No community discussion yet for this question.