Question 80
Several engineers use one shared admin account and no one can identify who changed a high-impact ACL. Which configuration or administrative response BEST addresses the primary issue?
Explanation
Correct Answer
Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. The platform may host audit capabilities, but customers must configure and review appropriate access and business-process controls. Verify prerequisites with: Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.
Incorrect Answers
Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. This approach instead addresses Workflow Studio debugging and Run As privileges. Flow execution identity and action permissions affect outcomes; rerunning as an administrator may hide missing delegation rather than fix it. The targeted response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.
Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. This approach instead addresses Scoped application permissions and cross-scope access. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The targeted response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.
Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. This approach instead addresses Tenant data handling and retention governance. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. The targeted response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.


