The answer is controlled by runtime behavior, not by naming similarity. The Platform App Builder role is to choose the standard Salesforce capability that owns the behavior: data structure, access, automation, user experience, reporting, or deployment. Choose D. Create an Apps Trigger on the Account object. This is the option that best matches the Salesforce responsibility being tested under Business Logic and Process Automation.
A practical administrator would confirm the object context, the user action, and whether the result must be stored, calculated, displayed, automated, approved, or deployed. Here the selected answer is the one that acts at the correct point in that chain. It keeps the configuration declarative and avoids inventing a process around a problem that Salesforce already has a native feature to solve.
The other options fall short for clear platform reasons. A (Remove the Delete permission from the Sales Rep profile.) is not enough: Permission controls are essential for access, but they do not perform calculations or process automation. B (Remove the delete button on the account layout.) handles a different concern; it handles only part of the requirement and leaves the controlling Salesforce behavior unresolved. C (Create a validation rule on the Account object.) is less defensible because A validation rule blocks saves; it does not create records, route approvals, display components, or grant access. Before release, test the configuration with the affected profile and realistic records, not only with a system administrator account.
---