Question 20
A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?
Explanation
Correct Answer
The script reads or changes only intended records with approved permission boundaries and predictable performance. GlideRecord is a server-side record API; code correctness and secure user-level data access are separate concerns requiring enforcement. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.
Incorrect Answers
Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. This result would support CMDB health completeness correctness and relationship audits, not the specific outcome required in the case. The relevant acceptance test is: The script reads or changes only intended records with approved permission boundaries and predictable performance. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.
One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications. This result would support Business Rule recursion and idempotent side effects, not the specific outcome required in the case. The relevant acceptance test is: The script reads or changes only intended records with approved permission boundaries and predictable performance. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.
The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup. This result would support Client server scripting with GlideAjax and scoped APIs, not the specific outcome required in the case. The relevant acceptance test is: The script reads or changes only intended records with approved permission boundaries and predictable performance. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.


