Reading a Unity Catalog table requires privileges at all relevant levels of its three-part namespace. The group needs USE CATALOG on corp_marketing, USE SCHEMA on campaigns, and SELECT on email_stats. These privileges allow users to resolve the catalog and schema and read the table without granting permission to create or modify objects. Option A omits USE CATALOG, so table access is incomplete. Option B unnecessarily grants CREATE SCHEMA, violating the requirement that the group must not create objects. Option D omits USE CATALOG and grants MODIFY, which would permit data changes. Unity Catalog follows a hierarchical permissions model, but possession of SELECT alone is insufficient without the required usage privileges on the parent containers. Therefore, the least-privilege sequence in option C is correct.

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