Which statement is true about tabletop exercises in DR/BC testing?

Which statement is true about tabletop exercises in DR/BC testing?

• A. They involve live changes to production systems.
• B. They are exclusively written drills with no discussion.
• C. They are a discussion-based scenario walkthrough to evaluate response without affecting live systems.
• D. They require downtime for the exercise.

Answer: (C)

Tabletop exercises test the team's decision-making and coordination in disaster recovery and business continuity by walking through a realistic scenario in a discussion-based format. They focus on how people would respond, who communicates with whom, escalation paths, and action planning, all without touching or altering any live systems. This approach lets participants analyze responsibilities, refine plans, and identify gaps, while keeping production environments untouched. That’s why this option is the best fit: it describes a discussion-based scenario walkthrough designed to evaluate response without affecting live systems. It isn’t just a written drill with no discussion, because tabletop exercises rely on guided conversation and scenario exploration. Also, they don’t require downtime or changes to production; they’re typically conducted in a meeting setting with no operational impact.

Tabletop exercises test the team's decision-making and coordination in disaster recovery and business continuity by walking through a realistic scenario in a discussion-based format. They focus on how people would respond, who communicates with whom, escalation paths, and action planning, all without touching or altering any live systems. This approach lets participants analyze responsibilities, refine plans, and identify gaps, while keeping production environments untouched.

That’s why this option is the best fit: it describes a discussion-based scenario walkthrough designed to evaluate response without affecting live systems. It isn’t just a written drill with no discussion, because tabletop exercises rely on guided conversation and scenario exploration. Also, they don’t require downtime or changes to production; they’re typically conducted in a meeting setting with no operational impact.