The correct answer is C. Dynamic Actions, as explicitly stated in the uploaded study guide. Dynamic Actions allow actions displayed on a Lightning record page to vary according to specified conditions. This is exactly what Cloud Kicks needs because users only require particular actions at particular record statuses.
Instead of displaying every available action at all times, the designer can configure visibility rules so that relevant actions appear contextually. This reduces visual clutter in the Highlights panel and helps users focus on actions that make sense at the current stage of the workflow.
Option A, Audiences, is primarily used to tailor Experience Cloud or Lightning content for particular user groups or contexts. It does not directly solve conditional record-action visibility based on record state.
Option B, Dynamic Forms, controls field and field-section placement and visibility. Dynamic Forms can simplify a record page by displaying relevant fields conditionally, but the requirement here specifically concerns action buttons, making Dynamic Actions the correct capability.
From a UX standpoint, contextual actions support recognition over recall and reduce decision fatigue. Users should not have to mentally filter a long list of irrelevant commands before locating the action they need.
Study Guide reference/topics: Dynamic Actions, Highlights Panel, Lightning Record Pages, conditional visibility, Declarative Design.
==================================
