ServiceNow CAD Practice Test 31
Question 300
A committed state change should trigger appropriate follow-on work. An engineer must explain the recommendation for After Business Rule related records. Which underlying principle is the MOST accurate?
- onChange execution receives old and new values and a loading flag.
- After rules run after database operations and can react to persisted changes.
- Script Includes support reusable server-side JavaScript rather than copying logic across rules.
- Async Business Rules decouple suitable after-commit work from the interactive transaction.
Explanation
Correct Answer
B:After rules run after database operations and can react to persisted changes. Therefore the implementation decision is to use an after Business Rule for post-save related actions, avoiding recursion.
Incorrect Answers
A:Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail. This describes the separate onChange client script guards mechanism; the present case instead requires After Business Rule related records.
C:Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail. Script Includes support reusable server-side JavaScript rather than copying logic across rules.
D:Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail. This describes the separate Async Business Rule processing mechanism; the present case instead requires After Business Rule related records.
Question 301
A release team wants to reconcile divergent source histories safely. Testing exposes this failure: Assuming Studio can perform every Git conflict merge can risk source loss. Which remediation should be applied FIRST?
- Use supported source control retrieval or pull operations after reviewing branch and local changes.
- Declare every possible branch merge supported natively by every ServiceNow Studio version.
- Configure supported Studio source control integration to the approved remote repository.
- Use documented Studio operations and external reviewed Git merging when necessary.
Explanation
Correct Answer
D:Use documented Studio operations and external reviewed Git merging when necessary. Confirmation requires seeing that the approved branch contains reviewed resolution and ServiceNow imports the intended revision.
Incorrect Answers
A:Use supported source control retrieval or pull operations after reviewing branch and local changes. It addresses Retrieve upstream source changes, not the diagnosed Branch and merge limitations in platform integration failure. Assuming Studio can perform every Git conflict merge can risk source loss.
B:Declare every possible branch merge supported natively by every ServiceNow Studio version. This retains the Branch and merge limitations in platform integration problem. Native integration capabilities vary and not all Git merge operations are supported inside Studio.
C:Configure supported Studio source control integration to the approved remote repository. It addresses Link app to Git repository in Studio, not the diagnosed Branch and merge limitations in platform integration failure. Assuming Studio can perform every Git conflict merge can risk source loss.
Question 302
A developer accidentally creates a script include outside the target application. After the recommended Application picker and context change is implemented, which observation MOST directly verifies that it works?
- The resulting application file belongs to the intended app scope.
- Only permitted application callers can execute the supported utility.
- Navigation displays active modules in the expected sequence.
- Application files carry the correct scope identifiers and distinct names.
Explanation
Correct Answer
A:The resulting application file belongs to the intended app scope. This directly tests whether the Application picker and context goal was met. The active application determines ownership of many new configuration files.
Incorrect Answers
B:Only permitted application callers can execute the supported utility. This is evidence about Restricted cross-scope scripting, not direct proof of the required Application picker and context behavior. The relevant check is that the resulting application file belongs to the intended app scope.
C:Navigation displays active modules in the expected sequence. This is evidence about Active state and module ordering, not direct proof of the required Application picker and context behavior. The relevant check is that the resulting application file belongs to the intended app scope.
D:Application files carry the correct scope identifiers and distinct names. This is evidence about Application scope namespace, not direct proof of the required Application picker and context behavior. The relevant check is that the resulting application file belongs to the intended app scope.
Question 303
An application property stores an interval as text but a timer expects a number. An engineer must explain the recommendation for Parse property types explicitly. Which underlying principle is the MOST accurate?
- Subflows support reusable automation with explicit input and output contracts.
- Server-side property access can supply configuration with optional default values.
- Property APIs may return strings and require explicit type interpretation.
- Configuration data can affect production behavior as seriously as code changes.
Explanation
Correct Answer
C:Property APIs may return strings and require explicit type interpretation. Therefore the implementation decision is to parse and validate property strings into the expected data types before using them.
Incorrect Answers
A:Treating nonempty false text as truthy can enable a feature unintentionally. This describes the separate Reusable subflow design mechanism; the present case instead requires Parse property types explicitly.
B:Treating nonempty false text as truthy can enable a feature unintentionally. Server-side property access can supply configuration with optional default values.
D:Treating nonempty false text as truthy can enable a feature unintentionally. Configuration data can affect production behavior as seriously as code changes.
Question 304
A service owner wants a field required when priority is high without writing browser code. Testing exposes this failure: A UI policy cannot replace ACL enforcement or every server-side data validation. Which remediation should be applied FIRST?
- Configure form layout or Form Designer sections and organize fields by user task.
- Use declarative UI policy where adequate and test condition reversals.
- Configure tailored form views and assign views through supported mechanisms.
- Configure field hiding as the only protection for confidential data.
Explanation
Correct Answer
B:Use declarative UI policy where adequate and test condition reversals. Confirmation requires seeing that desktop form reacts as expected to condition changes during manual testing.
Incorrect Answers
A:Configure form layout or Form Designer sections and organize fields by user task. It addresses Form layout sections and field placement, not the diagnosed UI policies for required and visible fields failure. A UI policy cannot replace ACL enforcement or every server-side data validation.
C:Configure tailored form views and assign views through supported mechanisms. It addresses Multiple form views by persona, not the diagnosed UI policies for required and visible fields failure. A UI policy cannot replace ACL enforcement or every server-side data validation.
D:Configure field hiding as the only protection for confidential data. This retains the UI policies for required and visible fields problem. UI policies offer declarative client-facing form behavior for mandatory, visible and read-only states.
Question 305
High-priority cases should enter approval while ordinary cases follow a different path. If the relevant Flow conditions and branching safeguard is omitted, which outcome is the MOST directly associated failure?
- Hard-coded values can misroute actions when incoming records differ.
- Without step-level evidence a missing task can be wrongly blamed on the trigger.
- A missing condition may send every case to the privileged branch.
- Exposing a token in property values or logs can leak access to an external system.
Explanation
Correct Answer
C:A missing condition may send every case to the privileged branch. Conditional flow logic determines which actions execute based on evaluated inputs. The corrective approach is to test both true and false paths with representative records.
Incorrect Answers
A:Hard-coded values can misroute actions when incoming records differ. This failure pattern belongs chiefly to Flow Designer data pills; it is not the failure most directly tested in the Flow conditions and branching situation. A missing condition may send every case to the privileged branch.
B:Without step-level evidence a missing task can be wrongly blamed on the trigger. This failure pattern belongs chiefly to Flow execution logs and troubleshooting; it is not the failure most directly tested in the Flow conditions and branching situation. A missing condition may send every case to the privileged branch.
D:This failure pattern belongs chiefly to Properties are not a secret vault; it is not the failure most directly tested in the Flow conditions and branching situation.
Question 306
An application owner needs to locate whether an email failed creation or delivery. An engineer must explain the recommendation for Email delivery troubleshooting. Which underlying principle is the MOST accurate?
- Email troubleshooting distinguishes notification selection from actual delivery status.
- Data pills carry typed step and trigger outputs through a flow.
- Notifications select recipients and content based on events or record conditions.
- Inbound email handlers can map received messages into application behavior.
Explanation
Correct Answer
A:Email troubleshooting distinguishes notification selection from actual delivery status. Therefore the implementation decision is to inspect notification conditions, outbound email records and delivery status using authorized tools.
Incorrect Answers
B:A successful trigger record does not guarantee the message was delivered. This describes the separate Flow Designer data pills mechanism; the present case instead requires Email delivery troubleshooting.
C:A successful trigger record does not guarantee the message was delivered. This describes the separate Email notification trigger and condition mechanism; the present case instead requires Email delivery troubleshooting.
D:A successful trigger record does not guarantee the message was delivered. Inbound email handlers can map received messages into application behavior.
Question 307
A second custom app should not insert or delete records in the first app's table. Which practical correction or implementation decision is MOST directly appropriate?
- Authorize only documented target and operation combinations.
- Apply least-privileged cross-scope permissions and negative test operations.
- Configure application access and verify cross-scope denial and allowed interfaces.
- Enable every Create Read Update Delete option for all scopes without checking the integration contract.
Explanation
Correct Answer
B:Apply least-privileged cross-scope permissions and negative test operations. The intended behavior can be checked because authorized read requests succeed while forbidden cross-scope writes fail.
Incorrect Answers
A:Authorize only documented target and operation combinations. This could help Runtime cross-scope access tracking, but it does not resolve the Table application access and CRUD scope case. Table application access determines cross-scope operation possibilities beyond user permissions.
C:Configure application access and verify cross-scope denial and allowed interfaces. This could help Private scope protects internal application files, but it does not resolve the Table application access and CRUD scope case. Table application access determines cross-scope operation possibilities beyond user permissions.
D:Enable every Create Read Update Delete option for all scopes without checking the integration contract. This would not correct the Table application access and CRUD scope workflow. Making a table accessible from all scopes does not by itself authorize end users.
Question 308
A reporting navigation section must appear only to authorized analyst roles. Which approach BEST meets the requirement while respecting the system constraints?
- Declare records secure solely because the navigation module is invisible.
- Create or configure an application menu with the intended modules.
- Configure a list module with a tested filter appropriate to the user scenario.
- Apply appropriate menu and module role restrictions and independently enforce data ACLs.
Explanation
Correct Answer
D:Apply appropriate menu and module role restrictions and independently enforce data ACLs. Navigation visibility and table access are separate security concerns. Verification should demonstrate that authorized users see the module and unauthorized users cannot retrieve the protected data.
Incorrect Answers
A:Declare records secure solely because the navigation module is invisible. This is an unsafe or ineffective shortcut for Module and menu role visibility. Relying only on hidden navigation does not stop direct record requests.
B:Create or configure an application menu with the intended modules. This primarily addresses Application menu navigation, not the specific Module and menu role visibility decision. Here, navigation visibility and table access are separate security concerns.
C:Configure a list module with a tested filter appropriate to the user scenario. This primarily addresses Filtered module navigation, not the specific Module and menu role visibility decision. Here, navigation visibility and table access are separate security concerns.
Question 309
A shared app depends on another scoped utility and fails after partial installation. Which approach BEST meets the requirement while respecting the system constraints?
- Use the supported Application Repository distribution and installation workflow where applicable.
- Check required application dependencies and versions before installation.
- Review application records and installed version in My Company Applications or supported manager.
- Assume any exported app can run independently of all required plugins or packages.
Explanation
Correct Answer
B:Check required application dependencies and versions before installation. App installation requires compatible dependencies and platform conditions. Verification should demonstrate that the clean test instance resolves dependencies and executes smoke tests.
Incorrect Answers
A:Use the supported Application Repository distribution and installation workflow where applicable. This primarily addresses Application repository release distribution, not the specific App installation dependencies decision. Here, app installation requires compatible dependencies and platform conditions.
C:Review application records and installed version in My Company Applications or supported manager. This primarily addresses My Company Applications lifecycle, not the specific App installation dependencies decision. Here, app installation requires compatible dependencies and platform conditions.
D:Assume any exported app can run independently of all required plugins or packages. This is an unsafe or ineffective shortcut for App installation dependencies. Installing without a dependency plan can leave missing tables or APIs.
Question 310
A developer has internal helper scripts that should not be used by unrelated apps. After the recommended Private scope protects internal application files change is implemented, which observation MOST directly verifies that it works?
- Role-positive and role-negative tests produce the expected server-side branch.
- Authorized caller contexts invoke the API while unrelated contexts fail.
- Unrelated application contexts cannot invoke private files without permitted cross-scope access.
- A consumer installation respects configured artifact edit and visibility restrictions.
Explanation
Correct Answer
C:Unrelated application contexts cannot invoke private files without permitted cross-scope access. This directly tests whether the Private scope protects internal application files goal was met. Scope protection restricts application artifact usage across apps.
Incorrect Answers
A:Role-positive and role-negative tests produce the expected server-side branch. This is evidence about gs.hasRole server authorization, not direct proof of the required Private scope protects internal application files behavior. The relevant check is that unrelated application contexts cannot invoke private files without permitted cross-scope access.
B:Authorized caller contexts invoke the API while unrelated contexts fail. This is evidence about Script Include accessible from scope setting, not direct proof of the required Private scope protects internal application files behavior. The relevant check is that unrelated application contexts cannot invoke private files without permitted cross-scope access.
D:A consumer installation respects configured artifact edit and visibility restrictions. This is evidence about Protected application files and distribution, not direct proof of the required Private scope protects internal application files behavior. The relevant check is that unrelated application contexts cannot invoke private files without permitted cross-scope access.
