The correct answer is the one that enforces the intended result. Quick actions are compact, purpose-built entry points. They are especially effective in the mobile app because they reduce navigation, expose only the fields required for the task, and can prepopulate values. The correct response is therefore D. Global actions can be accessed anywhere actions are available in mobile including Record detail pages, feed, and Chatter groups.
The scenario is not asking for a feature list. It is asking which configuration produces the requested result with the fewest moving parts. A Salesforce app builder should favor a standard, visible Setup configuration whenever it fully meets the business need. That approach makes the build easier to validate in sandbox and easier to explain during release review.
The other options fall short for clear platform reasons. A (The global action ' s layout automatically clones the default page layout.) is not enough: Page layouts affect presentation; they do not grant the underlying object or field capability by themselves. B (Salesforce Lightning Component Library houses existing global actions prebuilt for use.) handles a different concern; A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. C (Global actions are record-specific and are available when searching that particular Object.) is less defensible because Actions improve user entry, but they are not a substitute for relationship modeling, reporting logic, or back-end automation. Before release, test the configuration with the affected profile and realistic records, not only with a system administrator account.
---