ServiceNow Vulnerability Response tables typically start with which prefix?
Correct Answer: D
Explanation:
In ServiceNow Vulnerability Response, most of the core tables follow the prefix sn_vul_, which is used for Vulnerability Response application data structures such as vulnerability findings, remediation tracking, and related records. This prefix helps clearly separate vulnerability-related tables from other ServiceNow application scopes and ensures consistent naming within the module.
Question 2
Changes made within a named Update Set in a different application scope:
Correct Answer: A, C
Explanation:
In ServiceNow, when you make changes inside a named Update Set, those changes are tracked and recorded in the update set even if you are working in a different application scope. Update Sets operate at the platform level, so they capture most configuration changes regardless of scope, as long as the update is supported and not restricted by scope boundaries. So cross-scope changes in a named Update Set are still captured (A), not ignored or partially saved.
Question 3
What is the minimum role required to create and change Service Level Agreements for Vulnerability Response groups?
Correct Answer: D
Explanation:
In ServiceNow Vulnerability Response, the minimum role required to create and modify Service Level Agreements (SLAs) for Vulnerability Response groups is sn_vul.admin, because SLA configuration for VR groups is restricted to administrative-level control within the Vulnerability Response application scope. Other roles:
sla_manager → generic SLA role, not sufficient for VR group SLA configuration
admin → broad platform access, but not the minimum required VR-specific role
sn_vul.vulnerability_write → allows record updates, not SLA configuration
So the correct answer is: D. sn_vul.admin
Demo Practice Mode
You are viewing only the questions marked as Demo.