The key is to separate behavior from appearance. The best answer is D. Patch. The decision turns on change- set deployment. Change sets move supported metadata between connected Salesforce environments. The receiving org uses inbound change sets and deployment validation to confirm whether the package can be deployed safely.
This is how the same requirement would be handled in a well-governed Salesforce org: identify the controlling object, relationship, field, page, automation, or environment first, and then configure the native capability for that control point. The selected answer satisfies the requirement without requiring users to perform extra interpretation or administrators to maintain an unnecessary custom workaround.
None of the other options gives the same administrative control. A (Roll) does not fit cleanly; it solves a symptom of the problem rather than the Salesforce mechanism that owns the result. B (Major) is only a partial match because it does not provide the same direct administrative control as the selected option. C (Minor) 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.
For deployment work, related metadata matters. Fields, layouts, actions, permissions, tabs, flows, and dependent components may all need to travel together for the target org to behave as expected.
---