Which workflow factors must be considered when designing an ECS solution?

Question

Options

• AComputing, capacity, and sizing
• BCurrent and future workflows and capacity
• CCurrent and future workflows and features
• DCapacity, performance, and features

• A
  3% (2)
• B
  2% (1)
• C
  6% (4)
• D
  89% (58)

Explanation

Option D is correct because when designing an Enterprise Content Services (ECS) solution, the three essential workflow factors are capacity (how much content the system must handle), performance (the speed and responsiveness required), and features (the functional capabilities needed to meet business requirements) - together these cover the technical, operational, and functional dimensions of the solution.

Option A ("Computing, capacity, and sizing") is wrong because "computing" and "sizing" are overlapping infrastructure concerns, not distinct workflow design factors, and the set omits the critical dimension of features. Option B ("Current and future workflows and capacity") incorrectly narrows focus to workflow planning and capacity alone, leaving out performance and features. Option C ("Current and future workflows and features") is the most tempting distractor - it sounds reasonable - but it conflates the design process (evaluating workflows) with actual design factors, and omits capacity/performance entirely.

Memory tip: Think of ECS design as a triangle - C.P.F. (Capacity, Performance, Features) - you need all three sides or the structure collapses. If an answer includes "current and future workflows," it's describing the analysis method, not the workflow factors themselves.

No community discussion yet for this question.