A permitting database EC2 host needs a simple, cost-effective boot disk plus a separately tuned data disk. What volume layout should the architect use?
Select an answer to reveal the explanation.
Short Explanation
Boot on sensible gp3, data on its own tuned volume—like keeping the engine oil separate from the cargo hold. You size and IOPS-tune the data disk without overpaying for the OS disk. One cold mush volume fights both jobs.
Full Explanation
Best practice volume layout often uses a general-purpose SSD such as gp3 for the boot/OS volume and one or more separate data volumes sized and IOPS-configured for the application. That separation lets architects tune performance and snapshots independently. Combining OS and DB on cold HDD, relying solely on ephemeral instance store for durable DB data, or striping many unnecessary boot volumes adds risk or complexity without benefit.