During a design review, an architect asks which choice best matches the IBM guidance. For IBM Certified watsonx Data Lakehouse Engineer, the topic is watsonx.data components. What should the team do?

Here's the deal: you would not ship a production change with no owner and no rollback plan. The same common sense applies here. 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. Coordinate storage, metadata, query engines, governance, and management interfaces as parts of one platform. That aligns with the Domain 2: watsonx.data Fundamentals 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 watsonx.data components requirement. - Option C is incorrect because it narrows the solution to one artifact or metric and misses the broader watsonx.data components requirement. - Option D is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. 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 the query workspace as the only component", "Manage access only in external BI tools", "Put all metadata in user spreadsheets") are distractors that don't fully capture the concept described.