A production admin would not solve this by decoration. 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 B. User will be presented with a ' Record Lock ' notification. 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 remaining answers do not control the same Salesforce behavior. A (User will be able to edit the description field only.) would be fragile here because it could produce an inconsistent result once different users, records, or apps are tested. C (User will be able to edit the name, but unable to edit the description.) is only a partial match because it does not provide the same direct administrative control as the selected option.
D (User will see the record is now owned by their manager.) misses the mark because it addresses a neighboring feature area rather than the exact behavior requested. The result is a cleaner app design because the behavior is handled by the feature Salesforce built for that purpose.
---