A senior engineer reviews the current plan and notices that one key control is missing. For IBM Certified watsonx Data Lakehouse Engineer, the topic is ingestion design. 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. Choose ingestion patterns that preserve schema, quality, and governance expectations. That aligns with the Domain 4: Data Integration 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 ingestion design requirement described in the scenario. - Option C is incorrect because it skips the control or validation that makes ingestion design reliable in production. - Option D is incorrect because it narrows the solution to one artifact or metric and misses the broader ingestion design requirement. 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 ("Load data without validating structure", "Skip metadata capture until after production", "Ingest only final dashboard aggregates") are distractors that don't fully capture the concept described.