Troubleshooting SAP HANA EBS Performance — High Latency and Queue Depth
A company runs SAP S/4HANA on AWS with a single-instance deployment. The database is hosted on an r5.8xlarge instance with 5000 provisioned IOPS EBS volumes. Recently, the system experienced a performance degradation during peak hours. CloudWatch metrics show that the EBS volume read latency is consistently above 10 ms, and the queue length is frequently peaking at 20. The instance is in the same Availability Zone as the EBS volumes. What should the administrator do to resolve the performance issue?
Quick Answer
The CloudWatch metrics described here point directly at an IOPS bottleneck: read latency consistently above 10 ms combined with a queue length peaking at 20 means I/O requests are piling up faster than the volume can service them, which is the classic signature of a workload demanding more IOPS than the volume is currently provisioned for. Increasing provisioned IOPS from 5000 to 10000 addresses this at the source by raising the ceiling on how many I/O operations per second the volume can handle, which reduces both the queue depth, since requests get serviced faster and don't back up as much, and the resulting latency. The explanation rules out other explanations for the slowdown by process of elimination: because the instance and its EBS volumes are in the same Availability Zone, cross-AZ network latency isn't a contributing factor, and because the data needs to persist reliably for a production SAP HANA database, ephemeral instance store volumes aren't a viable alternative regardless of their speed. This distinguishes an IOPS-capacity problem from other kinds of storage performance issues, like network latency or storage type mismatches, that would show different metric signatures. When you see sustained high read latency paired with a growing queue length on a provisioned-IOPS EBS volume, and same-AZ placement is confirmed, that combination points toward simply provisioning more IOPS to match the actual workload demand.
⚠ Common exam trap
It's easy for candidates to assume high latency is due to network distance (Option A) or that gp3 volumes always provide better performance (Option D), but the key metric is queue length, which directly points to IOPS exhaustion on the provisioned IOPS volume.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Increase the provisioned IOPS on the EBS volumes to 10000.
The CloudWatch metrics show high read latency (>10 ms) and a queue length peaking at 20, which indicates that the EBS volume is throttling due to insufficient IOPS for the workload. Increasing provisioned IOPS from 5000 to 10000 directly addresses the bottleneck by allowing more I/O operations per second, reducing queue depth and latency. Since the instance and volumes are in the same Availability Zone, network latency is not a factor, and instance store volumes are ephemeral and unsuitable for persistent SAP HANA data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Move the instance to a different Availability Zone to reduce network latency.
Why it's wrong here
Instance and EBS are already in same AZ; moving AZ would not help EBS latency.
- ✓
Increase the provisioned IOPS on the EBS volumes to 10000.
Why this is correct
Higher IOPS reduces latency and queue depth, improving performance.
- ✗
Move the database to an instance with instance store volumes for better performance.
Why it's wrong here
Instance store is ephemeral and not suitable for persistent database storage.
- ✗
Migrate the EBS volumes to gp3 volume type with baseline performance.
Why it's wrong here
gp3 may not meet the required IOPS; io1/io2 with higher IOPS is needed.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,616 original PAS-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PAS-C01
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company runs SAP S/4HANA on AWS and notices high latency in database transactions. The database is hosted on an r5.24xlarge instance with 768 GB of EBS gp3 storage. The SAP application servers are in the same VPC but different subnets. What should be changed to reduce latency?
hard- A.Use a smaller instance type to reduce network hops.
- B.Place the database instance in a cluster placement group with the application servers.
- C.Enable EBS optimization on the database instance and ensure the instance type supports dedicated EBS bandwidth.
- ✓ D.Change the EBS volume type to io2 Block Express with maximum IOPS.
Why D: Gp3 volumes may not provide the low latency required for SAP HANA database transactions. Switching to io2 Block Express volumes offers higher and more consistent IOPS with lower latency, which can reduce high database transaction latency. Option C is misleading because EBS optimization is already enabled by default on r5 instances, so 'enabling' it is not a valid change.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PAS-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PAS-C01 exam.