During a design review, an architect asks which choice best matches the IBM guidance. The team is focused on predictive vs exploratory analytics. Which recommendation is most appropriate?

Here's the deal: this is where a demo turns into an operation. The design has to survive real users, real failures, and real audits. In this scenario, answer B 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 B. Use exploratory analytics for discovery and predictive analytics for model-driven forecasting or scoring. That aligns with the Domain 5: Consumption 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 sounds related, but it does not solve the predictive vs exploratory analytics requirement described in the scenario. - Option C is incorrect because it sounds related, but it does not solve the predictive vs exploratory analytics requirement described in the scenario. - Option D is incorrect because it skips the control or validation that makes predictive vs exploratory analytics reliable in production. 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 ("Treat ad hoc filtering as a trained predictive model", "Use predictive analytics when no target or history exists", "Avoid exploratory work before modeling") are distractors that don't fully capture the concept described.