In ECS Solution Design, which practices are effective for monitoring and improving the performance of stateless applications?

Question

Options

• AHorizontal scaling based on load
• BMonitoring connection pool sizes
• CRegularly updating the desktop backgrounds of ECS instances
• DImplementing auto-scaling policies based on performance metrics

• A
  82% (32)
• C
  18% (7)

Explanation

A (Horizontal scaling based on load) is correct because stateless applications are designed to scale out rather than up - adding more instances during high demand is the core advantage of statelessness, since any instance can handle any request without shared session state.

B (Monitoring connection pool sizes) is correct because even stateless apps depend on downstream resources (databases, APIs); saturated connection pools cause latency and failures, making pool monitoring a key performance signal.

D (Implementing auto-scaling policies based on performance metrics) is correct because auto-scaling automates the response to performance changes (CPU, request rate, latency), ensuring capacity matches demand without manual intervention.

C is wrong - updating desktop backgrounds has zero impact on application performance. It's a nonsense distractor designed to test whether candidates can distinguish meaningful operational practices from irrelevant administrative actions.

Memory tip: Think "SAP" - Scale out, Auto-scale policies, Pool monitoring. Any option that affects how resources respond to real workload signals is likely correct; anything cosmetic or unrelated to workload (like desktop backgrounds) is always a trap.

No community discussion yet for this question.