Which tool graphically displays an infrastructure view for a configuration item (CI) and its relationship with other CIs?
Correct Answer: B
The Dependency View graphically represents Configuration Items (CIs) and their relationships in ServiceNow's Configuration Management Database (CMDB). It provides an interactive visualization of dependencies and relationships between infrastructure components, helping administrators understand system architecture. Key Features of Dependency View: Displays CI relationships in an interactive graphical format. Helps identify upstream and downstream dependencies (e.g., how a failed server affects dependent applications). Can be accessed via the Configuration Item (CI) form under the Related Links section. Used in Impact Analysis for Change Management and Incident Management. Why Not Other Options? A . Schema Map - Used to visualize table relationships, not CI dependencies. C . Dependency Map - Not a ServiceNow term; the correct term is Dependency View. D . Database View - Used to create virtual tables combining data from multiple tables but does not display CI dependencies graphically. Reference: ServiceNow Dependency Views - Official Documentation
Question 137
Which one of the following modules can be used to view field settings for a table?
Correct Answer: D
Question 138
What is the difference between UI Policy and UI Action?
Correct Answer: A
Question 139
What is the path an Administrator could take to view the fulfillment stage task list for an order placed by a user?
Correct Answer: B
Question 140
How would you define an Access Control, to allow a user with iti role to have permission to create incident records?
Correct Answer: E
In ServiceNow, Access Control Rules (ACLs) are used to grant or restrict permissions for performing actions on a table or field. To allow a user with the itil role to create Incident records, the correct Access Control Rule must: Apply to the incident table Grant the "create" operation Be restricted to users with the "itil" role Breaking Down the Correct ACL Configuration: ACL Field Correct Value Name incident.None (applies to the table-level, not a field) Operation create (allows creating new records) Role itil (only users with the itil role can create incidents) Why is "incident.None" used instead of "incident.*"? incident.None → Applies to the entire table (for record creation). incident.* → Applies to all fields in the table (not needed for create operations). Incorrect Answer Choices Analysis: A . Name: incident"; Permission: write; Role: itil ❌ Incorrect - The "write" permission allows editing existing records, but does not allow creating new ones. B . Name: incident Any, Operation: write, Permission: itil ❌ Incorrect - There is no such name format "incident Any" in ACLs. Also, "write" does not allow record creation. C . Name: incident.*; Operation: write; Permission: itil ❌ Incorrect - "incident.*" applies to all fields in the table, but does not apply to record creation. D . Name: incident None, Permission: create: Role: itil ❌ Incorrect - The correct format uses "Operation: create", not "Permission: create". Official ServiceNow Documentation Reference: ServiceNow Docs - Access Control Rules 📖 How ACLs Work ServiceNow Docs - Configuring ACLs for Tables and Fields 📖 Table-Level vs Field-Level ACLs
