AD0-E117 · Question #23
A company is implementing a new e-commerce site that is expected to get seasonal and flash- sale induced traffic peaks from all over the world. It is projected that a minute of downtime could cause…
The correct answer is A. Scalability E. Usability. There appears to be an error in the provided answer key. Based on the scenario, the correct answers should be A (Scalability) and B (Availability) - not A and E. Here's why: Scalability (A) is correct because the system must handle unpredictable traffic spikes from seasonal…
Question
A company is implementing a new e-commerce site that is expected to get seasonal and flash- sale induced traffic peaks from all over the world. It is projected that a minute of downtime could cause excessive lost revenue. The company management wants to keep resource utilization to optimal levels without experiencing degradation to avoid introducing bugs in the system. The Architect needs to choose between AEM 6.5 and AEM as Cloud Service. What are the two most critical non-functional requirements the Architect must consider? (Choose two.)
Options
- AScalability
- BAvailability
- CReliability
- DMaintainability
- EUsability
How the community answered
(35 responses)- A43% (15)
- B20% (7)
- C29% (10)
- D9% (3)
Explanation
There appears to be an error in the provided answer key. Based on the scenario, the correct answers should be A (Scalability) and B (Availability) - not A and E.
Here's why:
Scalability (A) is correct because the system must handle unpredictable traffic spikes from seasonal events and flash sales without degrading performance. AEM as a Cloud Service's auto-scaling capability directly addresses this need.
Availability (B) is correct - not Usability (E) - because the question explicitly states "a minute of downtime could cause excessive lost revenue." High availability is the defining requirement here, and it's a core differentiator of AEM as a Cloud Service (zero-downtime deployments, auto-recovery).
Why the other options are less critical here:
- Reliability (C) overlaps with availability but focuses on consistent behavior over time rather than uptime itself - availability is the more precise fit.
- Maintainability (D) matters for long-term code health but isn't a primary concern for revenue loss from downtime.
- Usability (E) refers to ease of use for end users or developers - the scenario gives no indication this is a concern, making it the clear outlier.
Memory tip: When a question mentions traffic spikes → think Scalability; when it mentions revenue loss from downtime → think Availability. These two are the classic "black Friday e-commerce" NFR pair.
If this is from an official AEM certification prep resource, I'd recommend double-checking the source - the scenario strongly contradicts E as a correct answer.
Topics
Community Discussion
No community discussion yet for this question.