Which database operations can be controlled with Application Access? (Choose 2 answers)
Correct Answer: A,D
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."
Question 7
Which one of the following database operations cannot be controlled with Application Access?
Correct Answer: D
Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. You can use Application Access to control the following database operations: Create: This operation allows the user to create new records on the table. You can enable or disable this operation by selecting or clearing the Can create option. Delete: This operation allows the user to delete existing records on the table. You can enable or disable this operation by selecting or clearing the Can delete option. Read: This operation allows the user to view the records on the table. You can enable or disable this operation by selecting or clearing the Can read option. Write: This operation allows the user to modify the records on the table. You can enable or disable this operation by selecting or clearing the Can write option. The one database operation that cannot be controlled with Application Access is Query. Query is not an operation, but a method of the GlideRecord class that is used to retrieve records from the database on the server-side. Query is not part of the Application Access rules, but it is affected by the Access Controls and the user's roles. Reference: Application Access [GlideRecord methods]
Question 8
Which of the following is true about deleting fields from a table?
Correct Answer: B
User-defined non-inherited fields can be deleted from a table in ServiceNow. These are fields that are created by users on a specific table and are not inherited from a parent table. Inherited fields cannot be deleted from a table, as they are defined on a parent table and shared by all child tables. Any field on a table cannot be deleted, as some fields are system-defined and essential for the table functionality. Table records are not deleted when a field is deleted, as the field deletion only affects the table structure and not the data. Reference: Delete fields
Question 9
Which one of the following is NOT a debugging strategy for client-side scripts?
In ServiceNow, Modules are navigation elements that provide access to various parts of the platform, such as forms, lists, reports, or other application components. They are organized within Application Menus to create a structured and intuitive navigation hierarchy. Key characteristics of Modules: * Part of Application Menus: Every module is contained within an application menu. This organization helps users navigate to different areas of the platform efficiently. For instance, the "Incident" application menu may contain modules like "Create New" or "All Incidents." * Functionality: Modules can open various elements, including forms, lists, reports, or URLs. This flexibility allows modules to direct users to specific records, filtered lists, or external resources. * Association with Tables: While many modules are associated with specific tables (e.g., a module that displays a list of incidents is associated with the "Incident" table), it's not a strict requirement. Some modules may link to external URLs or perform actions not directly tied to a table. * Access Control: Access to modules is controlled through roles. Administrators can define which user roles have visibility and access to specific modules, ensuring that users only see modules relevant to their responsibilities. For example, a module named "Active Incidents" under the "Incident" application menu might display a list of all active incident records. Access to this module can be restricted to users with the "itil" role, ensuring that only authorized personnel can view active incidents.
