The answer is to examine Oracle database wait events for enqueue and latch contention, as these directly reveal internal database locking issues that cause slow SAP NetWeaver response times even when CPU utilization is low. When CPU is idle, the bottleneck is often not processing power but rather resource contention or I/O waits; enqueue waits indicate row-level locking conflicts, while latch contention points to memory structure serialization, both of which stall transactions without taxing the CPU. On the AWS Certified SAP on AWS Specialty PAS-C01 exam, this scenario tests your ability to differentiate between compute-bound and concurrency-bound performance problems—a common trap is to assume low CPU means the database is fine, but you must check wait events and also verify network throughput via CloudWatch metrics like NetworkIn/Out. Remember the mnemonic “Low CPU, Check Locks and Links”—meaning first inspect Oracle wait events for locks, then validate network links between app and database servers.
PAS-C01 Design of SAP Workloads on AWS Practice Question
This PAS-C01 practice question tests your understanding of design of sap workloads on aws. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An SAP administrator is troubleshooting a performance issue on an SAP NetWeaver system running on AWS. The system uses an Oracle database. The CPU utilization of the database server is consistently below 30%, but application response times are slow. Which THREE checks should the administrator perform to identify the bottleneck?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Amazon CloudWatch metrics to check network throughput and latency between the application and database servers.
Option A is correct because high network latency or insufficient throughput between the application and database servers can cause slow response times even when CPU utilization is low. Amazon CloudWatch metrics such as NetworkIn, NetworkOut, and NetworkPacketsIn/Out can reveal congestion or bandwidth saturation, which is a common bottleneck in SAP NetWeaver deployments on AWS.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Use Amazon CloudWatch metrics to check network throughput and latency between the application and database servers.
Why this is correct
Network latency can cause slow responses.
Related concept
Read the scenario before looking for a memorised answer.
✓
Check the EBS volume queue length and I/O wait times on the database server.
Why this is correct
High queue length indicates I/O bottleneck.
Related concept
Read the scenario before looking for a memorised answer.
✓
Examine Oracle database wait events for enqueue and latch contention.
Why this is correct
Database locks can cause slow responses.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the number of CPU cores on the database server.
Why it's wrong here
CPU is already underutilized.
✗
Enable Amazon EBS Elastic Volumes to increase volume size dynamically.
Why it's wrong here
Volume size does not directly fix performance.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume low CPU utilization means the system is not busy, overlooking that I/O wait, network latency, or database contention can cause slow responses without consuming CPU cycles.
Detailed technical explanation
How to think about this question
Under the hood, SAP NetWeaver with Oracle relies on efficient network communication for SQL*Net traffic; high latency or packet loss can cause TCP retransmissions and increased wait times. EBS volume queue length exceeding the recommended threshold (e.g., >1 per volume) indicates I/O saturation, while Oracle wait events like 'enq: TX - row lock contention' or 'latch free' point to internal database locking issues that degrade performance without high CPU usage.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design of SAP Workloads on AWS — This question tests Design of SAP Workloads on AWS — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Amazon CloudWatch metrics to check network throughput and latency between the application and database servers. — Option A is correct because high network latency or insufficient throughput between the application and database servers can cause slow response times even when CPU utilization is low. Amazon CloudWatch metrics such as NetworkIn, NetworkOut, and NetworkPacketsIn/Out can reveal congestion or bandwidth saturation, which is a common bottleneck in SAP NetWeaver deployments on AWS.
What should I do if I get this PAS-C01 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.