The key is to separate behavior from appearance. The best answer is D. Public group. The scenario is asking for approval governance, and the reason is straightforward: Approval processes are designed for formal review. They route a request, capture a decision, and can lock or update the record through submission and final actions. The wording points to this control because the business result must be reliable when real users work with real records.
For the stated requirement - Cloud Kicks (CK) captures all shipping information in a custom object called Shipments_c. CK ' s app builder is tasked with creating an approval process to ensure department members can approve all overnight shipments. - the selected answer handles the behavior directly. It is not just a way to make the page look cleaner or to remind users what to do. It places the responsibility in the Salesforce feature that owns the outcome. That matters in an App Builder implementation because access, automation, relationships, page rendering, reporting, and deployment each have different enforcement points.
None of the other options gives the same administrative control. A (Role) does not fit cleanly; it solves a symptom of the problem rather than the Salesforce mechanism that owns the result. B (Queve) is only a partial match because it does not provide the same direct administrative control as the selected option. C (Hierarchy fiele) misses the mark because it addresses a neighboring feature area rather than the exact behavior requested. This is the stronger design because it respects security, data quality, user experience, and lifecycle management at the same time.
---