Your organization is running a critical production database on a virtual machine (VM) on Compute Engine. The VM has an ext4-formatted persistent disk for data files. The database will soon run out of

Question

Options

• AIn the Google Cloud Console, increase the size of the persistent disk, and use the resize2fs
• BIn the Google Cloud Console, increase the size of the persistent disk, and use the fdisk command
• CIn the Google Cloud Console, create a snapshot of the persistent disk, restore the snapshot to a
• DIn the Google Cloud Console, create a new persistent disk attached to the VM, and configure the

• A
  76% (22)
• B
  14% (4)
• C
  7% (2)
• D
  3% (1)

Explanation

Options C and D introduce unnecessary complexity: creating a snapshot and restoring to a larger disk requires detaching the original disk (causing downtime), and adding a new separate disk requires reconfiguring the database to use a new storage path, which is disruptive. Option B is wrong because fdisk is a partition table editor, not a filesystem resize tool; using it on a live partition with a running database risks data corruption and does not resize the ext4 filesystem. Option A is correct: Google Cloud Compute Engine supports online persistent disk resizing - you can increase the disk size through the Console without stopping the VM or detaching the disk. After resizing the block device, resize2fs can extend an ext4 filesystem online (while it is mounted and in use) to utilize the newly allocated space. This entire process requires zero downtime.

No community discussion yet for this question.