Free ServiceNow CAD Practice Exam with Questions & Answers | Set: 2

Creating applications in ServiceNow can help businesses replace outdated, inadequate, custom business applications and processes, extend service delivery and management to all enterprise departments, and extend the value of ServiceNow by leveraging its platform capabilities and integrations1234.

References = 1: What are Application Services? - ServiceNow 2: What is Application Development? - ServiceNow 3: Custom Applications in ServiceNow - The Cloud People 4: Build Custom Apps in ServiceNow – eBook – ServiceNow

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/guided-app-creator.html

Recurring checks, like finding task records that are unassigned, are implemented using platform automation that runs on a schedule. ServiceNow provides two common development-aligned places for this type of logic. Scheduled Script Execution is a scheduled job mechanism that runs server-side scripts at defined intervals. Developers use it to query tables (such as Task) and take actions like updating fields, creating follow-up records, or sending notifications when conditions are met. This matches option C. For low-code automation, Flow Designer also supports scheduled triggers, allowing developers to run a flow at specific times or on a repeating schedule to perform checks and actions. This matches option A (Scheduled Flows). Discovery Schedules are specific to the Discovery feature set for scanning infrastructure and are not used for general task management checks. “System Schedules” is not the standard construct where custom recurring business logic is authored for application development; the platform’s scheduled logic is typically implemented through scheduled jobs (including script executions) and scheduled flow triggers.

ServiceNow applications can be shared through supported deployment channels. Publishing to the ServiceNow Store makes the application available for broader distribution, typically after meeting Store requirements. Publishing to an application repository allows sharing within an organization or controlled repository model. Publishing to an Update Set creates an update set containing the current version of the application configuration records, which can then be transferred to another instance. A local drive, USB device, or spreadsheet is not a supported application publishing destination in the CAD application-development model. These may store exported files or documentation, but they are not proper application publishing targets. Therefore, A, C, and F are correct.

================

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

ServiceNow Studio code search uses the default code search group to determine which application file types are searchable. To expand the supported file types, an administrator can create a new code search group that includes additional file types. This is cleaner than modifying a default table or changing unrelated metadata synchronization settings. The important CAD concept is that code search is metadata-driven and applies to searchable application file types, generally those extending sys_metadata. Creating a new code search group keeps the configuration controlled and avoids changing baseline behavior unnecessarily. Therefore, option A is the best answer for expanding supported Studio code search file types.

================

" Use an existing MID Server to connect to a Source Control repository. Linking or importing an application through a MID Server enables access to repositories behind a firewall. " https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/c_SourceControlIntegration.html

Application developers can specify which ServiceNow page a user sees after submitting a new record using the Record Producer UI by writing a script in the Record Producer’s Script field: producer.redirect = “ < URL > ”;. This script sets the redirect property of the producer object to the URL of the desired page. For example, producer.redirect = “home.do”; will redirect the user to the homepage after submitting the record. The other options are not valid ways to specify the redirect page for a Record Producer. Reference: Populate record producer data and redirect users

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.”