When designing a data collection system, what factors should be considered when assessing how often data needs to be collected? (Select all that apply)

Question

Options

• AVolume of data
• BBusiness requirements
• CData collection tool limitations
• DData source availability

• A
  95% (42)
• C
  2% (1)
• D
  2% (1)

Explanation

Assessing how often data needs to be collected is fundamentally a requirements and scale question, which is why Volume of data (A) and Business requirements (B) are correct. Volume directly impacts frequency - high-velocity data may need near-continuous collection while sparse data might only need periodic pulls. Business requirements define the why: SLAs, reporting cadences, and operational needs set the actual standard for how fresh data must be.

Why C and D are wrong: Data collection tool limitations (C) and data source availability (D) are implementation constraints, not factors in determining how often data needs to be collected. They influence what's possible, not what's required. A well-designed system identifies the need first, then addresses constraints separately.

Memory tip: Think "Need vs. Can." Business requirements and volume tell you how often you need to collect; tool limitations and source availability tell you how often you can. Exam questions about requirements focus on needs, not constraints.

No community discussion yet for this question.