A consultant is advising a customer that wants a scalable implementation. For IBM Certified watsonx Data Lakehouse Engineer, the topic is multi-engine approach. 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 A 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 A. Select the right engine for the workload while sharing governed data through the lakehouse. 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 B is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option C is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option D is incorrect because it sounds related, but it does not solve the multi-engine approach 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 ("Create isolated copies for every engine", "Use one engine for every workload regardless of fit", "Bypass governance when switching engines") are distractors that don't fully capture the concept described.