Examkin

Question

Difficulty: Very hardHigh-Performing and Scalable Storage Solutions

An enterprise is migrating a clustered database workload to Amazon EC2. The cluster consists of three nodes that require concurrent, shared read/write access to a single block storage volume. The database engine requires support for SCSI-3 Persistent Reservations to coordinate write operations, and must achieve a minimum performance of 80,000 IOPS80,000 \text{ IOPS} and 2,000 MB/s2,000 \text{ MB/s} throughput with sub-millisecond latency.

Which two configurations must the solutions architect implement to meet these storage requirements? (Select TWO.)

  1. Provision an Amazon EBS `io2` volume with the required capacity, IOPS, and throughput, and enable the Multi-Attach feature.Answer
  2. Launch the EC2 instances in the same Availability Zone, and attach the `io2` volume to all three instances.Answer
  3. C
    Launch the EC2 instances across multiple Availability Zones in the same AWS Region, and attach the `io2` volume to all three instances.
  4. D
    Provision an Amazon EBS `gp3` volume with custom provisioned performance, and enable the Multi-Attach feature.
  5. E
    Create an Amazon EFS file system with Provisioned Throughput set to 2,000 MB/s2,000 \text{ MB/s}, and mount the volume to all three instances.

Answer

Provision an Amazon EBS io2 volume with the required performance and enable Multi-Attach, then launch the EC2 instances in the same Availability Zone and attach the volume to all instances.
The database workload requires shared block storage with SCSI-3 Persistent Reservations. Amazon EBS io2 volumes configured with Multi-Attach support this capability and provide the required performance (80,000 IOPS80,000 \text{ IOPS} and 2,000 MB/s2,000 \text{ MB/s} throughput). Since EBS Multi-Attach is restricted to a single Availability Zone, the EC2 instances must be launched in the same Availability Zone.

Step-by-Step Solution

1
Analyze the technical requirements of the database cluster.
Identified requirements: block storage, SCSI-3 Persistent Reservations, concurrent write access from 3 nodes, at least 80,000 IOPS80,000 \text{ IOPS}, and 2,000 MB/s2,000 \text{ MB/s} throughput.
Understanding key constraints helps eliminate incompatible storage types like file systems (Amazon EFS).
2
Evaluate EBS volume types for Multi-Attach and performance capabilities.
Only EBS io2 (and io2 Block Express) volumes support Multi-Attach and can reach the performance targets of 80,000 IOPS80,000 \text{ IOPS} and 2,000 MB/s2,000 \text{ MB/s}. General Purpose SSD (gp3) volumes do not support Multi-Attach and are capped at lower performance limits.
Selecting the correct volume type ensures that both the multi-writer feature and performance SLAs are satisfied.
3
Determine the network topology constraint for Multi-Attach.
EBS Multi-Attach volumes can only be attached to instances within the same Availability Zone.
Ensures that the cluster instances are deployed in the same Availability Zone to allow successful volume attachment.

Key Concept

Amazon EBS Multi-Attach with io2 volumes supports cluster-aware applications requiring shared block storage with SCSI-3 Persistent Reservations, limited to a single Availability Zone.

Alternative Method

If cross-AZ resiliency is required for the database layer, instead of using EBS Multi-Attach at the storage level, you could implement application-level replication (e.g., PostgreSQL streaming replication or SQL Server Availability Groups) where each database node uses its own dedicated EBS io2 volume in a different Availability Zone.
Estimated Time:3m 0s
Rate this question

Topics

High-Performing and Scalable Storage Solutions

More questions from this topic