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

Here's the deal: access control 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. Set permissions so users and engines can access only the data and operations they are allowed to use. That aligns with the Domain 3: Operation 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 access control requirement described in the scenario. - Option B is incorrect because it sounds related, but it does not solve the access control requirement described in the scenario. - Option C is incorrect because it narrows the solution to one artifact or metric and misses the broader access control 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 ("Grant broad admin rights for convenience", "Put sensitive filters in optional dashboard notes", "Use object names as the only security boundary") are distractors that don't fully capture the concept described.