Demo Servicenow CAD Exam Questions

"You must first select read access to grant any other API record operation."
https://docs.servicenow.com/bundle/tokyo-applicationdevelopment/
page/build/applications/reference/r_TableApplicationAccessFields.html
The Application Access configuration fields control the access level for an application and
its tables.
The following Application Access configuration fields are not available configuration if the Can read
field is not selected:
Can create. This field determines whether users can create records on the application tables.
Can update. This field determines whether users can update records on the application tables.
Can delete. This field determines whether users can delete records on the application tables.
These fields are not available because they depend on the Can read field, which determines whether
users can view records on the application tables. If users cannot read records, they cannot create,
update, or delete them either.
The following Application Access configuration fields are available regardless of the Can read
configuration field:
All access to this table via web services. This field determines whether users can access the
application tables using web services, such as REST or SOAP.
Allow configuration. This field determines whether users can configure the application tables, such
as adding or modifying fields, views, or indexes.

Reference: Application Access, Certified Application
Developer (CAD) Learning Path

https://developer.servicenow.com/dev.do#!/learn/learningplans/

rome/new_to_servicenow/app_store_learnv2_scripting_rome_debugging_client_scripts

The following are debugging strategies for client-side scripts, which run in the web browser and
manipulate the user interface:
g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of
the form.
Field Watcher. This is a debugging tool that displays the current and previous values of one or more
fields on a form.
jslog(). This is a client-side API that writes a message to the browser console.
The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run
on the ServiceNow platform and manipulate the database:
gs.log(). This is a server-side API that writes a message to the system log.
Reference: Client-Side
Scripting APIs, Debugging Client Scripts

To see what scripts, reports, and other application artifacts will be in a published application, the
best option is to examine the Application Files Related List in the application to be published. This
will show all the application files that belong to the application, grouped by file type and scope. You
can also filter, sort, or search the list to find specific files.
The following options are not the best ways to see what application artifacts will be in a published
application:
Enter the name of the Application in the Global search field. This will perform a global text search on
the instance and return any records that match the application name, which may include irrelevant
or incomplete results.
Open the list of Update Sets for the instance. This will show all the update sets that have been
created or imported on the instance, but not necessarily the ones that belong to the application to
be published. Update sets are used to move customizations between instances, not to publish
applications to the ServiceNow Store or Share.
Open the artifact records individually to verify the value in the Application field. This will require
opening each record that may be part of the application and checking the Application field, which is
tedious and error-prone.

Reference: Publish an Application, Application Files