A project lead is turning a proof of concept into a governed production workflow. For IBM Certified watsonx Data Lakehouse Engineer, the topic is cloud object storage. What should the team do?

Here's the deal: cloud object storage is not just a checkbox; it is the difference between a clean handoff and a late-night recovery call. In this scenario, answer D 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 D. Use object storage as scalable, durable lakehouse storage while managing metadata and access controls. That aligns with the Domain 1: Data Lakehouse 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 sounds related, but it does not solve the cloud object storage requirement described in the scenario. - Option B is incorrect because it skips the control or validation that makes cloud object storage reliable in production. - Option C is incorrect because it sounds related, but it does not solve the cloud object storage 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 ("Treat object storage like a local POSIX filesystem", "Avoid object storage because SQL cannot query it", "Store credentials in table names") are distractors that don't fully capture the concept described.