An administrator is troubleshooting a pilot deployment and wants the most appropriate next step. What is the best way to handle Query workspace and history while staying aligned with the certification objectives?

Here's the deal: think of Query workspace and history like labeling the cables before you close the rack door. If you skip that discipline, troubleshooting gets ugly fast. In this scenario, answer C is the practical move because it keeps the implementation tied to the real IBM capability instead of chasing a shortcut. The other choices sound tempting, but they either skip governance, ignore operational reality, or solve the wrong problem.

The correct answer is C. Use query workspace to run SQL and query history to review execution and troubleshoot behavior. That aligns with the Domain 3: Operation objective because it applies the feature or practice in the context where IBM expects a practitioner to use it. It also keeps the design reviewable, supportable, and realistic for a production environment.

Let's examine why the other options are incorrect: - Option A is incorrect because it narrows the solution to one artifact or metric and misses the broader Query workspace and history requirement. - Option B is incorrect because it removes visibility or governance at the exact point where the team needs it most. - Option D is incorrect because it sounds related, but it does not solve the Query workspace and history requirement described in the scenario. For the exam, connect the feature to the operational outcome: the right answer is the one that preserves control, accuracy, and maintainability instead of relying on a brittle shortcut. The incorrect options ("Troubleshoot failed SQL from storage bills only", "Delete query history to improve performance", "Use access control screens to write SQL") are distractors that don't fully capture the concept described.