ServiceNow CAD Practice Test 17
Question 160
A scheduled check reads a threshold that might not be configured in a new instance. A reviewer proposes this shortcut: Treat an absent property as a reliable Boolean true for every feature. Which principle BEST explains why a different solution is needed?
- Namespaced properties reduce configuration conflicts among unrelated applications.
- Application properties externalize configurable behavior from code.
- Data pills carry typed step and trigger outputs through a flow.
- Server-side property access can supply configuration with optional default values.
Explanation
Correct Answer
D:Server-side property access can supply configuration with optional default values. The appropriate approach is to read an application property using gs.getProperty with a safe documented fallback.
Incorrect Answers
A:Namespaced properties reduce configuration conflicts among unrelated applications. This is about Property naming in scoped applications, not why the proposed gs.getProperty with fallback shortcut should be rejected. Omitting default handling may lead to invalid comparisons or unintended behavior.
B:Application properties externalize configurable behavior from code. This is about Application properties for behavior toggles, not why the proposed gs.getProperty with fallback shortcut should be rejected. Omitting default handling may lead to invalid comparisons or unintended behavior.
C:Data pills carry typed step and trigger outputs through a flow. This is about Flow Designer data pills, not why the proposed gs.getProperty with fallback shortcut should be rejected. Omitting default handling may lead to invalid comparisons or unintended behavior.
Question 161
An analytics team proposes a custom app for low-latency scientific simulations. Which practical correction or implementation decision is MOST directly appropriate?
- Separate compute from workflow using a secure integration boundary.
- Run a GPU training job inside synchronous form business rules for every request.
- Prototype the data model and user workflow before committing to custom development.
- Document gaps and extend existing features where they meet the business need.
Explanation
Correct Answer
A:Separate compute from workflow using a secure integration boundary. The intended behavior can be checked because integration tests show platform records receive validated results without processing giant simulations.
Incorrect Answers
B:Run a GPU training job inside synchronous form business rules for every request. This would not correct the Avoid using platform as high-performance compute engine workflow. Executing massive compute loops inside business-rule transactions can degrade instance responsiveness.
C:Prototype the data model and user workflow before committing to custom development. This could help Workflow fit for scoped applications, but it does not resolve the Avoid using platform as high-performance compute engine case. A workflow platform is not a substitute for specialized large-scale numerical computing.
D:Document gaps and extend existing features where they meet the business need. This could help Reuse standard capabilities versus bespoke application, but it does not resolve the Avoid using platform as high-performance compute engine case. A workflow platform is not a substitute for specialized large-scale numerical computing.
Question 162
A user changes the request category and related guidance must refresh. An engineer must explain the recommendation for onChange client script guards. Which underlying principle is the MOST accurate?
- onChange execution receives old and new values and a loading flag.
- onSubmit scripts run in the client before the form is submitted.
- Removing a field from a form is different from removing the field from the table.
- onLoad scripts execute during form initialization, distinct from onChange or submit events.
Explanation
Correct Answer
A:OnChange execution receives old and new values and a loading flag. Therefore the implementation decision is to use onChange with checks for isLoading and the relevant old/new value.
Incorrect Answers
B:Ignoring the loading condition can produce unnecessary work while the form initializes. This describes the separate onSubmit client script validation mechanism; the present case instead requires onChange client script guards.
C:Ignoring the loading condition can produce unnecessary work while the form initializes. This describes the separate Remove fields from view without deleting data mechanism; the present case instead requires onChange client script guards.
D:Ignoring the loading condition can produce unnecessary work while the form initializes. This describes the separate onLoad client script initialization mechanism; the present case instead requires onChange client script guards.
Question 163
A code owner wants changes from a ServiceNow application tracked in version control. An engineer must explain the recommendation for Link app to Git repository in Studio. Which underlying principle is the MOST accurate?
- Git commits preserve source revisions so reviewers can trace changes.
- Repository synchronization requires explicit review of remote and local state.
- Delegated Development supports controlled non-admin development for eligible privately scoped applications.
- ServiceNow source control integration manages application metadata versions through repository operations.
Explanation
Correct Answer
D:ServiceNow source control integration manages application metadata versions through repository operations. Therefore the implementation decision is to configure supported Studio source control integration to the approved remote repository.
Incorrect Answers
A:Git commits preserve source revisions so reviewers can trace changes. This describes the separate Commit application changes to Git mechanism; the present case instead requires Link app to Git repository in Studio. Untracked manual editing can produce undocumented deployment drift.
B:Repository synchronization requires explicit review of remote and local state. This describes the separate Retrieve upstream source changes mechanism; the present case instead requires Link app to Git repository in Studio. Untracked manual editing can produce undocumented deployment drift.
C:Delegated Development supports controlled non-admin development for eligible privately scoped applications. This describes the separate Delegated Development for privately scoped apps mechanism; the present case instead requires Link app to Git repository in Studio. Untracked manual editing can produce undocumented deployment drift.
Question 164
A help desk needs ordinary incidents and assignments already supported by a core app. If the relevant Reuse standard capabilities versus bespoke application safeguard is omitted, which outcome is the MOST directly associated failure?
- A proof of concept that bypasses release gates can introduce unreviewed artifacts.
- Executing massive compute loops inside business-rule transactions can degrade instance responsiveness.
- Duplicating an existing product workflow can fragment reporting and upgrades.
- A valid table alone does not guarantee the desired navigation grouping.
Explanation
Correct Answer
C:Duplicating an existing product workflow can fragment reporting and upgrades. Reusing platform capabilities reduces duplicate schemas and unnecessary maintenance. The corrective approach is to document gaps and extend existing features where they meet the business need.
Incorrect Answers
A:A proof of concept that bypasses release gates can introduce unreviewed artifacts. This failure pattern belongs chiefly to Scoped app lifecycle planning; it is not the failure most directly tested in the Reuse standard capabilities versus bespoke application situation. Duplicating an existing product workflow can fragment reporting and upgrades.
B:Executing massive compute loops inside business-rule transactions can degrade instance responsiveness. This failure pattern belongs chiefly to Avoid using platform as high-performance compute engine; it is not the failure most directly tested in the Reuse standard capabilities versus bespoke application situation. Duplicating an existing product workflow can fragment reporting and upgrades.
D:A valid table alone does not guarantee the desired navigation grouping. This failure pattern belongs chiefly to Application menu navigation; it is not the failure most directly tested in the Reuse standard capabilities versus bespoke application situation. Duplicating an existing product workflow can fragment reporting and upgrades.
Question 165
A new feed labels one column differently from the app's field name. Which practical correction or implementation decision is MOST directly appropriate?
- Rename only the CSV filename and assume the column mapping is corrected.
- Stage files and inspect source field definitions before transforming.
- Test representative field maps with sample import rows.
- Choose a stable unique key and test re-import idempotency.
Explanation
Correct Answer
C:Test representative field maps with sample import rows. The intended behavior can be checked because imported records show correct target columns and mapped references.
Incorrect Answers
A:Rename only the CSV filename and assume the column mapping is corrected. This would not correct the Transform map source-to-target mapping workflow. An unconfigured map can leave target fields blank or misdirect values.
B:Stage files and inspect source field definitions before transforming. This could help CSV file data source and import set, but it does not resolve the Transform map source-to-target mapping case. Transform Maps determine how import set fields populate target table fields.
D:Choose a stable unique key and test re-import idempotency. This could help Coalesce for update versus insert, but it does not resolve the Transform map source-to-target mapping case. Transform Maps determine how import set fields populate target table fields.
Question 166
A developer considers putting an API token in an ordinary readable application property. An engineer must explain the recommendation for Properties are not a secret vault. Which underlying principle is the MOST accurate?
- Event and notification configuration separates business events from message formatting.
- Application properties externalize configurable behavior from code.
- Ordinary configuration properties should not be assumed suitable for protected secrets.
- Configuration data can affect production behavior as seriously as code changes.
Explanation
Correct Answer
C:Ordinary configuration properties should not be assumed suitable for protected secrets. Therefore the implementation decision is to store sensitive credentials in a supported secure credential mechanism and use properties for nonsecret settings.
Incorrect Answers
A:Exposing a token in property values or logs can leak access to an external system. This describes the separate Event-driven email versus synchronous code mechanism; the present case instead requires Properties are not a secret vault.
B:Exposing a token in property values or logs can leak access to an external system. This describes the separate Application properties for behavior toggles mechanism; the present case instead requires Properties are not a secret vault.
D:Exposing a token in property values or logs can leak access to an external system. Configuration data can affect production behavior as seriously as code changes.
Question 167
A Script Include needs to branch according to group membership under authorized rules. Which practical correction or implementation decision is MOST directly appropriate?
- Evaluate group membership against authenticated identity and use ACLs.
- Scope and document the property and preserve real ACL enforcement.
- Give access because the client posts a string naming the required group.
- Emit accurate messages after validating the operation and its outcome.
Explanation
Correct Answer
A:Evaluate group membership against authenticated identity and use ACLs. The intended behavior can be checked because positive and negative membership tests reflect the caller's assigned group relationships.
Incorrect Answers
B:Scope and document the property and preserve real ACL enforcement. This could help gs.getProperty server configuration, but it does not resolve the gs.getUser().isMemberOf group membership case. Effective group membership should come from server-side identity rather than form text.
C:Give access because the client posts a string naming the required group. This would not correct the gs.getUser().isMemberOf group membership workflow. Treating a free-form group name as membership proof bypasses authorization.
D:Emit accurate messages after validating the operation and its outcome. This could help gs.addInfoMessage user feedback, but it does not resolve the gs.getUser().isMemberOf group membership case. Effective group membership should come from server-side identity rather than form text.
Question 168
An approved app requires a reusable validation Script Include from another app. If the relevant Script Include accessible from scope setting safeguard is omitted, which outcome is the MOST directly associated failure?
- Granting access based on either unrelated condition alone may bypass intended restrictions.
- Arbitrary edits to foreign-scope ACLs can break isolation and fail permissions.
- Unrestricted cross-scope method calls can bypass planned encapsulation.
- Marking all utilities public increases unnecessary coupling and attack surface.
Explanation
Correct Answer
C:Unrestricted cross-scope method calls can bypass planned encapsulation. Cross-scope API exposure should be intentional to protect app boundaries. The corrective approach is to expose the minimum supported interface and verify caller policy.
Incorrect Answers
A:Granting access based on either unrelated condition alone may bypass intended restrictions. This failure pattern belongs chiefly to Access control condition versus role; it is not the failure most directly tested in the Script Include accessible from scope setting situation. Unrestricted cross-scope method calls can bypass planned encapsulation.
B:Arbitrary edits to foreign-scope ACLs can break isolation and fail permissions. This failure pattern belongs chiefly to Scope context and security rule ownership; it is not the failure most directly tested in the Script Include accessible from scope setting situation. Unrestricted cross-scope method calls can bypass planned encapsulation.
D:Marking all utilities public increases unnecessary coupling and attack surface. This failure pattern belongs chiefly to Private scope protects internal application files; it is not the failure most directly tested in the Script Include accessible from scope setting situation. Unrestricted cross-scope method calls can bypass planned encapsulation.
Question 169
An operations owner needs a safe recovery plan for a failed app update. Which practical correction or implementation decision is MOST directly appropriate?
- Compare installed version and update history before changing the app.
- Document dependencies and test install on a representative target.
- Declare production fully ready because the package appears in the application list.
- Run a post-install acceptance checklist with an approved recovery plan.
Explanation
Correct Answer
D:Run a post-install acceptance checklist with an approved recovery plan. The intended behavior can be checked because a failed deployment is detected and a supported rollback or remediation path is available.
Incorrect Answers
A:Compare installed version and update history before changing the app. This could help My Company Applications lifecycle, but it does not resolve the Post-install validation and rollback case. Installation success alone does not validate full business behavior.
B:Document dependencies and test install on a representative target. This could help App installation dependencies, but it does not resolve the Post-install validation and rollback case. Installation success alone does not validate full business behavior.
C:Declare production fully ready because the package appears in the application list. This would not correct the Post-install validation and rollback workflow. Users may see broken forms or permissions after an incomplete release test.
Question 170
A field change should update a help message without running on initial form population. A reviewer proposes this shortcut: Treat every onChange invocation during load as a confirmed user edit. Which principle BEST explains why a different solution is needed?
- GlideAjax enables supported asynchronous calls from client logic to server Script Includes.
- onChange execution receives old and new values and a loading flag.
- Catalog variables are user inputs that require explicit mapping or producer script logic.
- onLoad scripts execute during form initialization, distinct from onChange or submit events.
Explanation
Correct Answer
B:OnChange execution receives old and new values and a loading flag. The appropriate approach is to use onChange with checks for isLoading and the relevant old/new value.
Incorrect Answers
A:GlideAjax enables supported asynchronous calls from client logic to server Script Includes. This is about GlideAjax asynchronous client-server pattern, not why the proposed onChange client script guards shortcut should be rejected. Ignoring the loading condition can produce unnecessary work while the form initializes.
C:Catalog variables are user inputs that require explicit mapping or producer script logic. This is about Producer variable mapping, not why the proposed onChange client script guards shortcut should be rejected. Ignoring the loading condition can produce unnecessary work while the form initializes.
D:OnLoad scripts execute during form initialization, distinct from onChange or submit events. This is about onLoad client script initialization, not why the proposed onChange client script guards shortcut should be rejected. Ignoring the loading condition can produce unnecessary work while the form initializes.
