Which option is part of an implementation strategy?

Question

Options

• Asequence of major work packages or projects
• Bdesign criteria for meeting security requirements
• Cmaintenance schedule for hardware
• Danticipated transaction volumes during periods of maximum activity

• A
  92% (45)
• B
  2% (1)
• C
  4% (2)
• D
  2% (1)

Explanation

Option A is correct because an implementation strategy defines the high-level approach for executing a plan - specifically, how major work packages or projects will be sequenced and phased over time. It answers "how and in what order will we deliver this?"

Why the distractors are wrong:

• B (design criteria for security requirements) belongs to the design phase, not implementation strategy - it's a technical specification, not a sequencing plan.
• C (hardware maintenance schedule) is an operations/support concern that comes after implementation, not part of the strategy for rolling it out.
• D (anticipated transaction volumes at peak activity) is a capacity planning or performance requirement - input data used during design, not a component of the implementation strategy itself.

Memory tip: Think of an implementation strategy as a project roadmap - it tells you the order of the big moves. If the concept sounds like scheduling work packages or phasing deliverables, it's implementation strategy. If it sounds like technical specs, hardware ops, or performance metrics, it belongs elsewhere.

No community discussion yet for this question.