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

 The correct combination of statements is a, b, and d. These are possible reasons to build custom applications on ServiceNow:

To replace outdated, inadequate, custom business applications and processes. Building custom applications on ServiceNow can help digitize and automate manual or legacy processes that are not covered by existing ServiceNow solutions. This can improve efficiency, data quality, user experience, and innovation.

To extend service delivery and management to all enterprise departments. Building custom applications on ServiceNow can help provide consistent and scalable services across different functions and teams in the organization. This can enhance collaboration, visibility, productivity, and customer satisfaction.

To extend the value of ServiceNow. Building custom applications on ServiceNow can help leverage the capabilities and benefits of the Now Platform®, such as low-code development tools, workflow automation engine, AI-powered insights, security operations, etc. This can increase agility, resilience, performance, and value.

The statement c is not a valid reason to build custom applications on ServiceNow:

To allow users full access to all ServiceNow tables, records, and fields. Building custom applications on ServiceNow does not imply granting users full access to all data and objects in ServiceNow. Access control rules still apply to custom applications and their components to ensure security and compliance. Reference: Build Custom Apps in ServiceNow – eBook

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. References: 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_evaluation_order

This class allows you to create and manipulate dialog windows on the user interface. You can use this class to display messages, forms, or custom HTML content in a modal window.

GuideAjex: This class allows you to make asynchronous calls to the server and process the response. You can use this class to retrieve data, execute scripts, or perform actions on the server without reloading the page.

GuideForm: This class allows you to access and manipulate the fields and values on a form. You can use this class to get or set field values, show or hide fields, add or remove options, or validate field inputs.

The class GuideRecord is not part of the Client side scoped APIs. GuideRecord is part of the Server side scoped APIs, which are a set of classes and methods that allow you to interact with the database and perform server-side logic on the ServiceNow platform. GuideRecord is a class that represents a record in a table and allows you to query, insert, update, or delete records on the server.

The "Enforcing" mode ensures all cross-scope access is explicitly approved, logging and requiring manual approval if missing.

From ServiceNow Docs – Cross-Scope Access Controls:

“Enforcing mode logs cross-scope access attempts and blocks access unless explicit permission is granted.”

Application Access settings on a table control which operations external applications (in other scopes) can perform. The main controllable operations are:

Can create

Can read (query)

Can update

Can delete

From Development Handbook 4.0.4, p. 192:

“Application access settings determine whether another scope can read, write, create, or delete records from this table... Execute is not a valid database operation — it pertains to script includes or other executable logic.”

While record producers are powerful tools for creating records via the Service Catalog, they cannot natively redirect users after submission. Redirection typically requires script hacks or custom widget configurations.

From ServiceNow Docs (Catalog Scripting):

“By default, record producers return the user to the catalog homepage. Redirection requires scripting using producer scripts or custom client logic.”

Delegated Development is intended to let administrators grant controlled development permissions to non-admin developers for a specific scoped application. Within that model, admins can allow delegated developers to work on application artifacts and administration tasks that are still limited to the application scope. One of the permitted areas is managing security artifacts, which includes creating and maintaining Access Controls (ACLs) and related security configuration for the application’s tables and resources. That aligns directly to option C. Administrators can also grant the permission to delete the scoped application, which aligns to option D and is treated as a high-impact capability that is explicitly controlled by delegated development permissions. By contrast, option A is not valid because delegated development is for scoped applications and does not grant authority to develop or deploy global applications. Option B is not a delegated development permission category; coalesce configuration is part of import/set-up behavior and is not represented as a delegated developer permission in the application development permission set.