The correct answer is that the Classic Load Balancer idle timeout setting is too low. This is because the default idle timeout for TCP connections on a Classic Load Balancer is 60 seconds, and if your SAP web dispatchers or application hold connections open longer—such as during long-running reports or user think time—without transferring data, the load balancer terminates the connection, causing intermittent timeouts. On the AWS Certified SAP on AWS Specialty PAS-C01 exam, this scenario tests your understanding of how load balancer timeouts interact with SAP’s keep-alive behavior; a common trap is to blame the web dispatcher or network configuration instead. Remember that SAP applications often have longer idle periods than standard web apps, so the timeout must be increased to match. Memory tip: think “SAP sleeps, CLB weeps”—if SAP keeps the connection idle, the Classic Load Balancer will drop it.
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. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 system on AWS uses a Classic Load Balancer to distribute traffic to web dispatchers. The system is experiencing intermittent timeouts. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The load balancer idle timeout setting is too low.
The Classic Load Balancer has a default idle timeout of 60 seconds for TCP connections. If the SAP application or web dispatchers keep connections open longer than this without data transfer (e.g., during long-running reports or user think time), the load balancer will close the connection, causing intermittent timeouts. Increasing the idle timeout to match the application's keep-alive settings resolves this.
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.
✗
The security group for the load balancer is blocking traffic.
Why it's wrong here
Security groups would block connections entirely, not cause intermittent timeouts.
✗
Sticky sessions are enabled on the load balancer.
Why it's wrong here
Stickiness does not cause timeouts.
✗
The load balancer health check interval is too short.
Why it's wrong here
Health check interval affects health detection, not timeouts.
✓
The load balancer idle timeout setting is too low.
Why this is correct
Low idle timeout can cause premature connection termination.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse health check intervals with idle timeout, assuming a short health check interval causes timeouts, when in reality idle timeout is the direct cause of dropped connections during periods of inactivity.
Detailed technical explanation
How to think about this question
The Classic Load Balancer's idle timeout is configured per listener (TCP or HTTP/HTTPS). For SAP, which often uses long-lived HTTP connections for BSP applications or RFC calls, the default 60-second timeout can be insufficient. The timeout applies to both frontend (client to LB) and backend (LB to instance) connections independently; if either side exceeds the timeout, the connection is closed. Adjusting this value in the AWS console or via the AWS CLI (e.g., 'aws elb modify-load-balancer-attributes --load-balancer-attributes IdleTimeout=300') is a common fix.
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: The load balancer idle timeout setting is too low. — The Classic Load Balancer has a default idle timeout of 60 seconds for TCP connections. If the SAP application or web dispatchers keep connections open longer than this without data transfer (e.g., during long-running reports or user think time), the load balancer will close the connection, causing intermittent timeouts. Increasing the idle timeout to match the application's keep-alive settings resolves this.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.