Free ServiceNow® CAD Exam Braindumps (page: 9)

It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan.
What are some of the considerations to document as part of the business process?

  1. Business problem, data input/output, users/stakeholders, and process steps
  2. Business problem, data input/output, project schedule, and process steps
  3. Business problem, data input/output, users/stakeholders, and database capacity
  4. Business problem, users/stakeholders, available licenses, and database capacity

Answer(s): A

Explanation:

It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan. The following are some of the considerations to document as part of the business process:
Business problem. This is the description of the problem or opportunity that the application is intended to address or exploit. It should include the background, context, scope, and objectives of the problem or opportunity.
Data input/output. This is the specification of the data that the application will need to collect, store, manipulate, and display. It should include the data sources, formats, validations, transformations, and integrations of the data.
Users/stakeholders. This is the identification of the users and stakeholders who will be involved in or affected by the application. It should include the roles, responsibilities, expectations, and needs of the users and stakeholders.
Process steps. This is the definition of the steps and activities that the application will perform or support. It should include the inputs, outputs, triggers, conditions, and outcomes of each step or activity.
The following are not some of the considerations to document as part of the business process:
Project schedule. This is the estimation of the time and resources required to complete the application development project. It should include the milestones, deliverables, dependencies, and risks of the project. This is not part of the business process, but part of the project management plan. Database capacity. This is the measurement of the amount of data that the application will generate and store in the database. It should include the data volume, growth rate, retention policy, and backup strategy of the data. This is not part of the business process, but part of the technical design and architecture of the application.
Available licenses. This is the number and type of licenses that the application will consume or require from the ServiceNow platform. It should include the license model, cost, and allocation of the licenses. This is not part of the business process, but part of the financial and legal aspects of the application.


Reference:

Application Development Process, Business Process Analysis



Which of the following statements does NOT apply when extending an existing table?

  1. The parent table's Access Controls are evaluated when determining access to the new table's records and fields
  2. The new table inherits the functionality built into the parent table
  3. The new table inherits all of the fields from the parent table
  4. You must script and configure all required behaviors

Answer(s): D

Explanation:

You must script and configure all required behaviors Provided link has this statement: Extending an existing ServiceNow table means the new table inherits the parent table's columns as well as its business logic.

The following statements apply when extending an existing table:
The parent table's Access Controls are evaluated when determining access to the new table's records and fields. This is true because Access Control (ACL) rules are inherited from the parent table to the child table, unless the child table has its own ACL rules that override the parent table's rules. ACL rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user's roles and conditions.
The new table inherits the functionality built into the parent table. This is true because the new table inherits the business logic and the relationships from the parent table, such as Business Rules, Script Includes, UI Actions, UI Policies, and Reference Fields. Business logic and relationships are used to define the behavior and the structure of the data on the ServiceNow platform. The new table inherits all of the fields from the parent table. This is true because the new table inherits the columns and the attributes from the parent table, such as Field Name, Data Type, Default Value, and Mandatory. Columns and attributes are used to define the properties and the characteristics of the data on the ServiceNow platform. The following statement does not apply when extending an existing table:
You must script and configure all required behaviors. This is false because you do not have to script and configure all required behaviors when extending an existing table, as some of the behaviors are already inherited from the parent table, as explained above. However, you can script and configure additional or customized behaviors for the new table, such as adding new fields, creating new Business Rules, or modifying existing UI Actions.


Reference:

Table Extension, Access Control Rules



Which of the following CANNOT be debugged using the Field Watcher?

  1. Business Rules
  2. Script Includes
  3. Client Scripts
  4. Access Controls

Answer(s): D

Explanation:

The Field Watcher is a debugging tool that allows you to monitor the values of fields on a form as they change due to scripts or other actions. It can be used to debug Business Rules, Client Scripts, and Access Controls, but not Script Includes. Script Includes are server-side scripts that define reusable functions and classes. They are not associated with any specific field or form, and therefore cannot be watched by the Field Watcher.


Reference:

Field Watcher
Script Includes


https://docs.servicenow.com/bundle/orlando-application- development/page/script/debugging/ concept/c_FieldWatcher.html



Which objects can be used in Inbound Action scripts?

  1. current and previous
  2. current and email
  3. current and event
  4. current and producer

Answer(s): B

Explanation:

Inbound Action scripts are server-side scripts that run when an email is received by the system. They can use the current object to access the record that is created or updated by the email, and the email object to access the properties and methods of the email message. The previous and event objects are not available in Inbound Action scripts. The producer object is only available in Record Producer scripts, which are used to create records from a service catalog item.


Reference:

Inbound Action scripts
[Record Producer scripts]



Which one of the following is part of the client-side scripting API?

  1. workflow.scratchpad
  2. GlideUser object (g_user)
  3. current and previous objects
  4. GlideSystem object (gs)

Answer(s): B

Explanation:

https://developer.servicenow.com/dev.do#!/reference/api/rome/client The GlideUser object (g_user) is part of the client-side scripting API that provides information about the current user and the user's preferences. It can be used in Client Scripts and UI Policies to customize the user interface based on the user's role, language, time zone, etc. The workflow.scratchpad object is only available in Workflow scripts, which are used to automate processes on the platform. The current and previous objects are only available in server-side scripts, such as Business Rules and Script Includes. The GlideSystem object (gs) is also a server-side object that provides methods for logging, debugging, date and time calculations, etc.


Reference:

[GlideUser object (g_user)]
[Workflow scripts]
[Business Rules]
Script Includes
[GlideSystem object (gs)]



Viewing page 9 of 57
Viewing questions 41 - 45 out of 278 questions



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

CAD Exam Discussions & Posts