Question 740
An administrator hides an employee private identifier in the UI and presumes it cannot be read through the Table API. Which configuration or administrative response BEST addresses the primary issue?
Explanation
Correct Answer
Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Client-side policy alone does not protect API writes or data integrity; security and mandatory validation must be enforced at the appropriate server boundary. Verify prerequisites with: Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. Scenario: An administrator hides an employee private identifier in the UI and presumes it cannot be read through the Table API.
Incorrect Answers
Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. This approach instead addresses List filter conditions and breadcrumb logic. AND/OR grouping changes a list filter's meaning; a visual breadcrumb is not a proof the predicate selects the right records. The targeted response is: Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Scenario: An administrator hides an employee private identifier in the UI and presumes it cannot be read through the Table API.
Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. This approach instead addresses Business Rule recursion and idempotent side effects. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. The targeted response is: Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Scenario: An administrator hides an employee private identifier in the UI and presumes it cannot be read through the Table API.
Capture configuration changes in the appropriate update set and promote them through controlled development, test and production preview/commit stages. This approach instead addresses Update set creation completion and ordered promotion. Update sets track many configuration customizations, not arbitrary production business data; a named update set and preview are key controls. The targeted response is: Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Scenario: An administrator hides an employee private identifier in the UI and presumes it cannot be read through the Table API.


