A Data 360 Consultant wants to query data within a data model object (DMO).

A Query Editor workspace controls the objects and metadata that a user can query, and Salesforce requires the user to have data-space access to the object being queried. If the consultant created the workspace against the wrong data space, the required DMO will not appear in that workspace’s available object context. The clean corrective action is therefore to create a new workspace and select the data space that contains the DMO, making C correct. Adding the DMO to an unrelated data space changes governance and modeling rather than fixing the workspace selection. Merely referencing another data space in SQL does not bypass workspace and data-space access boundaries. The exam point is that workspace scope and data-space access determine which Data 360 objects Query Editor exposes.

================