Where can protection policies be applied?

• A. UI Actions, Script Includes
• B. Business Rules, Client Scripts
• C. Fields, Tables
• D. UI Policies, Data Policies

Answer: (A)

Protection policies are about restricting access to operations and ensuring security checks happen where actions are invoked. UI Actions are the direct entry points for user-triggered operations on forms and lists, so applying protection logic there determines which actions can be seen or executed by a user. Script Includes hold reusable code that can be called from multiple places, so placing protection logic in Script Includes ensures consistent enforcement across all code paths that might invoke that logic. Other areas like Fields and Tables are mainly about data structure, while Business Rules, Client Scripts, UI Policies, and Data Policies handle behavior and validation rather than centralized protection of operations. So, applying protection policies to UI Actions and Script Includes provides the most effective, centralized guardrails.