Question 60
A team shares one highly privileged service account for routine catalog changes and cannot attribute security modifications. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. The appropriate response is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Scenario: A team shares one highly privileged service account for routine catalog changes and cannot attribute security modifications.
Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. Verify prerequisites with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: A team shares one highly privileged service account for routine catalog changes and cannot attribute security modifications.
Incorrect Answers
Use ServiceNow access control diagnostics to identify the exact ACL evaluation blocking an authorized operation, preserving unrelated security checks. This step may apply to ACL debugging of roles conditions and scripts but is not one of the complementary requirements in this case. The intended pair is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Together with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: A team shares one highly privileged service account for routine catalog changes and cannot attribute security modifications.
A completed reviewed update set previews and commits successfully on test and production with expected configuration functionality. This step may apply to Update set creation completion and ordered promotion but is not one of the complementary requirements in this case. The intended pair is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Together with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: A team shares one highly privileged service account for routine catalog changes and cannot attribute security modifications.
Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. This step may apply to Scoped application permissions and cross-scope access but is not one of the complementary requirements in this case. The intended pair is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Together with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: A team shares one highly privileged service account for routine catalog changes and cannot attribute security modifications.


