Access Control debug information identification whether each element of an Access Control granted of denied access. The elements of an Access Control evaluated?
Correct Answer:C
The elements of an Access Control are evaluated in the following order: Conditions, Roles, Script. The Conditions are a set of criteria that must be met for the Access Control to apply. The Roles are a list of user roles that are required to access the object. The Script is an optional script that can further restrict or allow access based on custom logic. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Reference: Access control rules
* a. To replace outdated, inadequate, custom business applications and processes
* b. To extend service delivery and management to all enterprise departments
* c. To allow users full access to all ServiceNow tables, records, and fields
* d. To extend the value of ServiceNow
Correct Answer:D
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
Which method call returns true only if the currently logged in user has the catalog_admin role and in no other case?
Correct Answer:B
The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments. References: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]
Reference: https://community.servicenow.com/community? id=community_QUESTION
NO:&sys_id=dff705e6db7757c0d58ea345ca96196b
Which one of the following is true for a table with the “Allow configuration” Application Access option selected?
Correct Answer:C
The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. The following is true for a table with the Allow configuration option selected:
✑ Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.
The following are not true for a table with the Allow configuration option selected:
✑ Only the in scope application’s scripts can create Business Rules for the table.
This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.
✑ Any user with the application’s user role can modify the application’s scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application’s user role. To modify the application scripts, users need to have the admin role or the application’s admin role.
✑ Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application’s admin role and be in the application scope. References: Application Access, Business Rules
Reference: https://community.servicenow.com/community? id=community_QUESTION NO:&sys_id=1a721819dbfa23409a64e15b8a9619d2
Why would you build a custom app?
Correct Answer:A
A possible reason to build a custom app is to fulfill a specific use case on internal processes. For example, you may want to digitize a manual process that is not covered by an existing ServiceNow solution, such as managing inventory, tracking expenses, or scheduling events. Building a custom app on the Now Platform can help you automate workflows, improve data quality, and provide better user experiences. The other options are not valid reasons to build a custom app. To avoid using a code repository like GitHub or GitLab is not a reason to build a custom app, as you can still use source control integration with your custom app development. To create a custom integration for a 3rd party system is not a reason to build a custom app, as you can use integration tools such as IntegrationHub or REST APIs to connect with external systems without creating an app. To replace ServiceNow base tables is not a reason to build a custom app, as it is not recommended to modify or delete base tables that are essential for ServiceNow functionality. Reference: Build Custom Apps in ServiceNow – eBook