Amazon Web Services SOA-C02 Exam With Confidence Using Practice Dumps

AWS EBS snapshots are incremental, meaning that after the initial full snapshot, only the blocks that have changed since the last snapshot are saved. Here’s how the storage adds up based on your scenario:

First Snapshot: Captures all 10 GiB of data.

Second Snapshot: Only 4 GiB have changed, so only these changed blocks are stored.

Third Snapshot: An additional 2 GiB of data are added, making only these new 2 GiB stored.

Thus, the total storage required is 10 GiB (initial snapshot) + 4 GiB (second snapshot) + 2 GiB (third snapshot) = 16 GiB.

AWS Documentation Reference:

Details on how EBS snapshots store data can be found here: Amazon EBS Snapshots.

As demand on your clusters changes, you might decide to improve performance or reduce costs by changing the number of shards in your Redis (cluster mode enabled) cluster. We recommend using online horizontal scaling to do so, because it allows your cluster to continue serving requests during the scaling process.

Using ALB health checks in the Auto Scaling group will provide more accurate health monitoring and replace instances if they are unhealthy.

ALB Health Checks: Configure health checks based on HTTP response codes, which will detect application-level issues causing the HTTP 500 errors and replace instances as needed.

EC2 vs. ALB Health Checks: EC2 status checks only verify instance hardware and OS, not the application’s responsiveness. By using ALB health checks, Auto Scaling can remove instances that are failing at the application level, thus preventing users from receiving 500 errors.

Replacing the ALB with a Network Load Balancer does not address HTTP 500 errors, and enabling session affinity does not resolve application health issues. The CloudWatch agent would not provide the required health check functionality for automated instance replacement.