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

In ServiceNow, Access Controls (ACLs) are used to manage permissions for various database operations on tables and their records. The primary operations that can be controlled include:

Create:

Description: Permission to insert new records into a table.

Control: ACLs can be defined to allow or deny users the ability to create records based on roles, conditions, or scripts.

Update:

Description: Permission to modify existing records in a table.

Control: ACLs can restrict who can update records, ensuring that only authorized users can make changes.

Other Operations:

Read: Controls the ability to view records in a table.

Delete: Manages the permission to remove records from a table.

Incorrect Options:

Execute: Not a standard database operation controlled by ACLs in ServiceNow.

Query: While querying is part of the read operation, ACLs specifically control the read access rather than the query process itself.

Creating an Application Properties page in ServiceNow provides a centralized location where developers or administrators can configure settings that influence the behavior of an application. This approach offers several benefits:

Dynamic Configuration: By exposing certain parameters through an Application Properties page, administrators can adjust the application's behavior in response to changing requirements or environments without altering the underlying code or application artifacts.

Simplified Maintenance: Having a dedicated properties page reduces the need for direct modifications to scripts or configurations, thereby minimizing the risk of introducing errors. It also streamlines the process of updating settings, as changes can be made through the user interface.

Enhanced Flexibility: Developers can design applications with configurable options, allowing for greater adaptability across different

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_DefaultDesignAccessPermissions.html

The baseline behavior of a table in a privately-scoped application is that all application scopes can read from the table. A privately-scoped application is an application that restricts write access to its tables and resources to scripts within the same scope. However, read access is allowed by default for all scopes, unless the administrator explicitly denies it using an Access Control rule. This allows for data sharing between different applications while maintaining data integrity and security. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

ServiceNow provides several methods to install applications onto an instance, each suited to different scenarios:

Import an Application from an XML File (Option A):

Description: Developers can export an application as an XML file and then import it into another ServiceNow instance.

Use Case: This method is commonly used for moving applications between instances, such as from development to production.

Procedure:

Navigate to "System Applications" > "Applications."

Click on the "Import" button.

Upload the XML file of the application.

Update Sets group configuration changes for deployment across environments (e.g., from dev to test). They don’t track data or metrics.

From Development Handbook 4.0.4, p. 213:

“Update Sets are used to track and bundle changes, allowing developers to promote and test configuration updates between instances.”

 Extending an existing table such as the Task table when creating a new application has several benefits, such as:

You can repurpose existing fields by simply changing the label. For example, you can change the Short description field to Summary or Title for your new table.

You can use existing fields with no modifications. For example, you can use the Assigned to, Priority, and State fields for your new table without changing anything.

Existing logic from the parent table will be automatically applied to the new table. For example, you can inherit the Business Rules, Client Scripts, and UI Policies from the Task table for your new table.

The only option that is not true is d) All of the parent table records are copied to the new table. Extending a table does not copy any records from the parent table to the new table. It only creates a new table that inherits the fields and logic from the parent table.

Ensuring that users receive email notifications in ServiceNow requires verifying specific attributes on the user record:

A. The Email field must have a valid value: This is correct. The Email field should contain a valid email address, as notifications are sent to the address specified in this field.

B. The user must not be locked out: While it's important for user access, being locked out does not directly impact the sending of email notifications.

C. The First name and Last name fields must have values: These fields are for identification purposes and do not affect email notification delivery.

D. Active must be true: This is correct. Only active users are eligible to receive email notifications. If a user is marked as inactive, notifications will not be sent to them.

E. Delegation must be enabled: Delegation pertains to assigning responsibilities to another user and does not influence the receipt of email notifications.

For effective email notification delivery, always ensure that the user's Email field contains a valid address and that the Active field is set to true.

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html

"Application developers must select an application as their current scope context." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html