You are using AWS EC2 linux instance for log processing which would require high throughput. You chose Throughput optimized HDD storage with 500 GB in size. You deployed your application to production mode and it is running as expected. After a month, you see anincrease in log files and you are fast approaching the 500 GB size and running out of space onthe EBS volume. Which of the following is a best approach to mitigate the situation with minimal configuration?

Answer options:

A.Add a new EBS volume, mount on EC2 instance and configure your application accordingly.
B.Increase the size of the existing EBS volume.
C.EBS volume size cannot be changed. Build purging logic for your old log files
D.You can have only one EBS volume per instance. Snapshot existing EBS volume, detach current volume, create a new volume from snapshot with bigger size and attached to EC2 instance.

Answer: B
Although option A looks correct, it is not the best approach since it involves more configuration and changes to the application to point to a new EBS mount point.
Option B is correct.
You can modify the volume and increase in volume size.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modify-volume.html
Option C is incorrect. The reason for Option C to be wrong is, we can increase the volume size but the option mentioned about "EBS volume size cannot be changed` is the reason.
Option D is not correct. You can attach multiple EBS volumes to the single EC2 instances.