nerdexam
Amazon

SOA-C02 · Question #245

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 sys

The correct answer is A. Extend the file system with operating system-level tools to use the new storage capacity.. After you increase the size of an EBS volume, use the Windows Disk Management utility or PowerShell to extend the disk size to the new size of the volume. You can begin resizing the file system as soon as the volume enters the optimizing state. https://docs.aws.amazon.com/AWSEC2/

Submitted by layla.eg· Mar 30, 2026Monitoring, Logging, and Remediation

Question

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 system. What should a SysOps administrator do to resolve this issue?

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

How the community answered

(56 responses)
  • A
    82% (46)
  • B
    11% (6)
  • C
    5% (3)
  • D
    2% (1)

Explanation

After you increase the size of an EBS volume, use the Windows Disk Management utility or PowerShell to extend the disk size to the new size of the volume. You can begin resizing the file system as soon as the volume enters the optimizing state. https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/recognize-expanded-volume-

Topics

#EBS volume resize#Windows file system extension#disk management#storage expansion

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice