Which of the following is NOT a recommended activity during the solutions design process for ECS?

Question

Options

• APrototyping and testing different configurations
• BIgnoring scalability and future expansion needs
• CEvaluating security and compliance requirements
• DGathering user feedback and requirements

• A
  5% (1)
• B
  95% (21)

Explanation

Ignoring scalability and future expansion needs (B) is the correct "NOT recommended" activity because any robust solutions design process must account for growth - failing to do so leads to costly redesigns, performance bottlenecks, and systems that quickly become inadequate.

The distractors are all genuinely recommended activities: A (prototyping and testing) validates design decisions early and reduces implementation risk; C (evaluating security and compliance) ensures the solution meets regulatory and organizational standards from the outset; and D (gathering user feedback and requirements) grounds the design in real-world needs rather than assumptions.

Memory tip: Think of the four pillars of good solutions design as "Test, Scale, Secure, Listen" - any answer that breaks one of these pillars is the wrong activity to include.

No community discussion yet for this question.