Cloud Kicks has a content-rich set of record pages and wants its UX Design team...

The correct answer is C. Tabs, as identified in the study guide. Tabs are used to divide related information into logical sections within the same interface. For a content-rich record page, they allow the UX team to consolidate substantial amounts of information without displaying every section simultaneously. This supports information hierarchy and reduces visual overload. Users can focus on the currently relevant category while retaining easy access to other related information through clearly labeled tab controls. Option A, Data Tables, is appropriate for presenting structured records in rows and columns. A table does not solve the broader requirement to organize several categories of record-page content. Option B, Modals, temporarily display focused information or actions above the current interface. They are useful for confirmation, short forms, or specific interactions, but they are not intended as the primary architecture for persistent record-page organization. The underlying UX principle is progressive disclosure: present the information required for the current task while keeping secondary content readily accessible. Tabs accomplish this without forcing users to leave the record page. Accordingly, for consolidating a content-heavy Salesforce record experience, the SLDS Tabs component offers the most appropriate structural pattern.

Study Guide reference/topics: SLDS Tabs, content organization, progressive disclosure, information hierarchy, component design.

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