Pass the ServiceNow Certified Application Developer CAD Questions and answers with CertsForce

The elements of an Access Control are evaluated in the following order: Conditions, Roles, Script. The Conditions are a set of criteria that must be met for the Access Control to apply. The Roles are a list of user roles that are required to access the object. The Script is an optional script that can further restrict or allow access based on custom logic. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Reference: Access control rules

In ServiceNow, extending a table means creating a new table (child class) that inherits properties from an existing table (parent class). This inheritance includes fields, business logic, and other configurations, allowing for efficient reuse and customization.

Key Points:

Field Inheritance: The child table inherits all fields from the parent table. For example, if you extend the Task table, your new table will include fields like " short_description " and " priority. "

Business Logic Inheritance: The child table also inherits business rules, client scripts, and other logic defined on the parent table, ensuring consistent behavior across related tables.

Access Controls: Access controls are not ignored; instead, the child table inherits the parent table ' s access controls. However, you can define additional access controls specific to the child table as needed.

Customization: While the child table inherits many properties, you can add new fields, scripts, and behaviors to tailor it to specific requirements without affecting the parent table.

The statements that must evaluate to true for a user to pass an Access Control are:

Conditions configured in the Access Control must evaluate to true.

The user has one of the roles specified in the Required roles related list.

Scripts configured in the Access Control must evaluate to true.

An Access Control is a rule that determines whether a user can access a particular object or operation in ServiceNow. An Access Control consists of three elements: Conditions, Roles, and Script. Each element specifies a requirement that the user must meet to access the object or operation. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Therefore, for a user to pass an Access Control, all three elements must evaluate to true.

The other statements are not required for a user to pass an Access Control. Other matching Access Controls for the records do not need to evaluate to true, as only one matching Access Control needs to return true for access to be granted. The user does not need to be granted access through a business rule, as business rules are not part of Access Controls and do not affect their evaluation. Reference: Access control rules, Access Controls

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html

When creating a table in a privately-scoped application, four Access Controls are automatically created for the table. These Access Controls define the permissions for the four basic operations on the table: Create, Delete, Read, and Write. The Create operation allows the user to create new records on the table. The Delete operation allows the user to delete existing records on the table. The Read operation allows the user to view the records on the table. The Write operation allows the user to modify the records on the table. By default, these Access Controls grant access to the admin role and the application scope. You can modify or delete these Access Controls as needed.

The other options are not valid Access Controls for a table. Insert, Query, and Update are not operations, but methods of the GlideRecord class that are used to manipulate records on the server-side. They are not part of the Access Control rules.

Definition of a Spoke:A " spoke " is a scoped application or component of an application that contains Flow Designer actions and integrations. Spokes provide reusable functionality and are typically used to extend the capabilities of Flow Designer.

Why It’s Called a Spoke:

Spokes are part of the ServiceNow Flow Designer framework.

They contain predefined actions that are reusable across multiple flows. For example, an " Email Spoke " might include actions for sending emails or managing email configurations.

Why Other Options Are Incorrect:

Option B (Flow): This refers to an individual flow, not the application containing reusable actions.

Option C (Bundle): There is no such term as " Bundle " specific to Flow Designer in ServiceNow.

Option D (Action): While flows contain actions, the scoped application that houses these actions is referred to as a spoke.

ServiceNow Developer Documentation on Flow Designer Spokes​.