Free ServiceNow® CAD Exam Braindumps (page: 7)

Which platform feature can be used to determine the relationships between field in an Import Set table to field in an existing ServiceNow table?

  1. Business Service Management Map
  2. Data Sources
  3. Transform Map
  4. Cl Relationship Builder

Answer(s): C

Explanation:

A transform map determines the relationships between fields displaying in an Import Set table and fields in an existing ServiceNow table, such as the Incidents or Users table.


Reference:

https://community.servicenow.com/community? id=community_QUESTION NO :&sys_id=69fc8369db9cdbc01dcaf3231f961935
The following platform feature can be used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Transform Map. This is a feature that defines the mapping between the fields of an Import Set table and the fields of a target table, such as incident, problem, or user. A transform map also specifies the logic and rules for transforming the imported data, such as coalescing, scripting, or applying data policies.

The following platform features are not used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Business Service Management Map. This is a feature that provides a graphical representation of the configuration items (CIs) and their relationships in the Configuration Management Database (CMDB). A Business Service Management Map can be used to visualize the impact of incidents, changes, or problems on the CIs and the services they support.
Data Sources. This is a feature that defines the connection and authentication information for an external data source, such as a file, a JDBC database, or a web service. A data source is used to import data from the external source into an Import Set table. CI Relationship Builder. This is a feature that creates relationships between CIs in the CMDB based on predefined or custom rules. A CI Relationship Builder can be used to populate the CMDB with the dependencies and connections between the CIs.


Transform Maps, Business Service Management Map, Data Sources, CI Relationship Builder



When configuring a REST Message, the Endpoint is:

  1. The commands to the REST script to stop execution
  2. The URI of the data to be accessed, queried, or modified
  3. Information about the format of the returned data
  4. The response from the provider indicating there is no data to send back

Answer(s): B

Explanation:

When configuring a REST Message, the Endpoint is:
The URI of the data to be accessed, queried, or modified. This is the correct answer because the Endpoint is the part of the REST Message that specifies the location and the resource of the REST provider. The Endpoint is composed of the base URL and the resource path, which can include query parameters or variables. For example, the Endpoint for a REST Message that retrieves the weather information for a city from a web service could be https://api.openweathermap.org/data/2.5/weather?q=London. The following are not correct definitions of the Endpoint when configuring a REST Message:
The commands to the REST script to stop execution. This is not correct because the commands to the

REST script to stop execution are not part of the REST Message, but of the Scripted REST API, which is a feature that allows users to create custom REST endpoints on the ServiceNow platform. The commands to the REST script to stop execution are methods of the RESTAPIResponse object, such as setStatusCode, setError, or complete.
Information about the format of the returned data. This is not correct because the information about the format of the returned data is not part of the Endpoint, but of the HTTP headers or the Accept field of the REST Message. The HTTP headers or the Accept field can be used to specify the content type of the response, such as JSON, XML, or HTML.
The response from the provider indicating there is no data to send back. This is not correct because the response from the provider indicating there is no data to send back is not part of the Endpoint, but of the HTTP status code or the response body of the REST Message. The HTTP status code or the response body can be used to indicate the result of the REST request, such as 200 OK, 404 Not Found,

or 500 Internal Server Error.


Reference:

REST Messages, Scripted REST APIs


https://docs.servicenow.com/bundle/orlando-application- development/page/integrate/outbound- rest/reference/r_RESTMessageElements.html



When evaluating Access Controls, ServiceNow searches and evaluates:

  1. Only for matches on the current table
  2. Only for matches on the current field
  3. From the most specific match to the most generic match
  4. From the most generic match to the most specific match

Answer(s): C

Explanation:

When evaluating Access Controls, ServiceNow searches and evaluates:
From the most specific match to the most generic match. This is the correct answer because ServiceNow follows a top-down approach when evaluating Access Control (ACL) rules, which are used to restrict the access to the data and functionality of the ServiceNow platform based on the user's roles and conditions. ServiceNow starts with the most specific match, which is the field-level ACL rule, then moves to the table-level ACL rule, and finally to the global or * ACL rule. ServiceNow grants access if any of the ACL rules evaluates to true, and denies access if all of the ACL rules evaluate to false.
The following are not correct descriptions of how ServiceNow searches and evaluates Access Controls:
Only for matches on the current table. This is not correct because ServiceNow does not only look for matches on the current table, but also on the parent tables and the global or * table. For example, if there is no ACL rule for the incident table, ServiceNow will look for an ACL rule for the task table, which is the parent table of the incident table, and then for the global or * table, which is the parent table of all tables.
Only for matches on the current field. This is not correct because ServiceNow does not only look for matches on the current field, but also on the table that contains the field and the global or * table. For example, if there is no ACL rule for the short_description field on the incident table, ServiceNow will look for an ACL rule for the incident table, and then for the global or * table.

From the most generic match to the most specific match. This is not correct because ServiceNow does not follow a bottom-up approach when evaluating Access Controls, but a top-down approach, as explained above.


Reference:

Access Control Rules, ACL Evaluation Order https://developer.servicenow.com/dev.do#!/learn/learning- plans/paris/new_to_servicenow/app_store_learnv2_securingapps_paris_access_controls_evaluatio n_order



In a Business Rule, which one of the following returns true if the currently logged in user has the admin role?

  1. g_form.hasRoleExactly(`admin')
  2. gs.hasRole(`admin')
  3. g_form.hasRole(`admin')
  4. gs.hasRoleExactly(`admin')

Answer(s): B

Explanation:

Business Rule is server-side, so it uses GlideSystem API. gs.hasRoleExactly doesn't exist

In a Business Rule, the following returns true if the currently logged in user has the admin role:
gs.hasRole(`admin'). This is the correct answer because gs is the GlideSystem object, which provides methods for performing system operations, and hasRole is a method that checks if the current user has the specified role. For example, gs.hasRole(`admin') will return true if the current user has the admin role, and false otherwise.
The following do not return true if the currently logged in user has the admin role in a Business Rule:
g_form.hasRoleExactly(`admin'). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRoleExactly is a method that checks if the current user has exactly the specified role and no other roles. For example, g_form.hasRoleExactly(`admin') will return true if the current user has only the admin role, and false if the current user has the admin role and any other role.
g_form.hasRole(`admin'). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRole is a method that checks if the current user has the specified role or any role that contains the specified role. For example, g_form.hasRole(`admin') will return true if the current user has the admin role or any role that contains the admin role, such as admin_ui or admin_script.
gs.hasRoleExactly(`admin'). This is not correct because gs is the GlideSystem object, which provides methods for performing system operations, and hasRoleExactly is not a valid method of the gs object. There is no method that checks if the current user has exactly the specified role and no other roles in the gs object.


Reference:

Business Rules, GlideSystem, GlideForm



From the list below, identify one reason an application might NOT be a good fit with ServiceNow.

The application:

  1. Needs workflow to manage processes
  2. Requires "as-is" use of low-level programming libraries
  3. Requires reporting capabilities
  4. Uses forms extensively to interact with data

Answer(s): B

Explanation:

From the list below, the following is a reason an application might not be a good fit with ServiceNow:
Requires "as-is" use of low-level programming libraries. This is the correct answer because ServiceNow is a high-level platform that abstracts away the low-level details of the underlying infrastructure and technology stack. ServiceNow provides a rich set of APIs, tools, and features that allow users to develop applications without coding or with minimal coding. However, ServiceNow does not support the direct



Viewing page 7 of 57
Viewing questions 31 - 35 out of 278 questions



Post your Comments and Discuss ServiceNow® CAD exam prep with other Community members:

CAD Exam Discussions & Posts