PAS-C01 · Question #78
A company is running its SAP system on AWS with a secondary SAP HANA database in a sidecar setup. The company requires high IOPS for write performance on its Amazon Elastic Block Store (Amazon EBS)…
The correct answer is B. Create a RAID 0 configuration with several EBS volumes. Creating a RAID 0 configuration across multiple EBS volumes aggregates the IOPS and throughput of each individual volume, effectively multiplying the available IOPS. Since the EC2 instance bandwidth is sufficient (ruling out the instance as the bottleneck), striping multiple…
Question
A company is running its SAP system on AWS with a secondary SAP HANA database in a sidecar setup. The company requires high IOPS for write performance on its Amazon Elastic Block Store (Amazon EBS) volumes for the secondary SAP HANA database. The EBS volume that the company uses for its SAP HANA data volume cannot provide the required IOPS. Instance bandwidth for the Amazon EC2 instance that is hosting the SAP HANA database is sufficient. An SAP solutions architect needs to propose a solution to resolve the IOPS performance issue. Which solution will achieve the required IOPS?
Options
- AReplace the EBS storage with EC2 instance store storage.
- BCreate a RAID 0 configuration with several EBS volumes.
- CUse Amazon EC2 Auto Scaling to launch Spot Instances.
- DCreate a placement group with several EBS volumes.
How the community answered
(26 responses)- A15% (4)
- B73% (19)
- C8% (2)
- D4% (1)
Explanation
Creating a RAID 0 configuration across multiple EBS volumes aggregates the IOPS and throughput of each individual volume, effectively multiplying the available IOPS. Since the EC2 instance bandwidth is sufficient (ruling out the instance as the bottleneck), striping multiple EBS volumes with RAID 0 is the standard AWS-recommended approach to exceed the per-volume IOPS limit. EC2 instance store (A) is ephemeral and not suitable for SAP HANA persistent data. Auto Scaling with Spot Instances (C) does not address storage IOPS and Spot Instances are inappropriate for production SAP HANA workloads. Placement groups (D) affect instance placement and network topology, not individual EBS volume IOPS.
Topics
Community Discussion
No community discussion yet for this question.