ServiceNow CAD Practice Test 4
Question 30
Two departments build similarly named business rules and tables. An engineer must explain the recommendation for Application scope namespace. Which underlying principle is the MOST accurate?
- Scoped apps isolate application artifacts and reduce naming collisions.
- Script includes and API access can be constrained across application scopes.
- The active application determines ownership of many new configuration files.
- ServiceNow application development suits record-centered business workflows with governed access.
Explanation
Correct Answer
A:Scoped apps isolate application artifacts and reduce naming collisions. Therefore the implementation decision is to build in the intended private application scope and use its generated namespace.
Incorrect Answers
B:Editing in Global by mistake can create uncontrolled shared metadata. Script includes and API access can be constrained across application scopes.
C:Editing in Global by mistake can create uncontrolled shared metadata. The active application determines ownership of many new configuration files.
D:Editing in Global by mistake can create uncontrolled shared metadata. This describes the separate Workflow fit for scoped applications mechanism; the present case instead requires Application scope namespace.
Question 31
A developer finishes a tested Script Include change and needs a source-history checkpoint. A reviewer proposes this shortcut: Assume pressing Save on a form always creates a Git commit. Which principle BEST explains why a different solution is needed?
- Git commits preserve source revisions so reviewers can trace changes.
- App installation requires compatible dependencies and platform conditions.
- Native integration capabilities vary and not all Git merge operations are supported inside Studio.
- Source control rights may be assigned separately from general delegated editing.
Explanation
Correct Answer
A:Git commits preserve source revisions so reviewers can trace changes. The appropriate approach is to commit the appropriate scoped application changes with descriptive revision metadata.
Incorrect Answers
B:App installation requires compatible dependencies and platform conditions. This is about App installation dependencies, not why the proposed Commit application changes to Git shortcut should be rejected. Changes left uncommitted can be missing from the agreed repository version.
C:Native integration capabilities vary and not all Git merge operations are supported inside Studio. This is about Branch and merge limitations in platform integration, not why the proposed Commit application changes to Git shortcut should be rejected. Changes left uncommitted can be missing from the agreed repository version.
D:Source control rights may be assigned separately from general delegated editing. This pertains to Delegated source-control authorization rather than the required Commit application changes to Git task. Git commits preserve source revisions so reviewers can trace changes.
Question 32
A pilot must move from development to test and then approved production. Which approach BEST meets the requirement while respecting the system constraints?
- Check the organization subscription and any custom-table entitlements before designing the schema.
- Treat a working personal developer instance as automatic production approval.
- Plan app scope, owners, test instances, dependencies and deployment checkpoints.
- Evaluate existing ServiceNow capabilities before building a new scoped application.
Explanation
Correct Answer
C:Plan app scope, owners, test instances, dependencies and deployment checkpoints. Application fit also includes operational ownership and promotion practices. Verification should demonstrate that a release checklist identifies owner, version, acceptance tests and rollback plan.
Incorrect Answers
A:Check the organization subscription and any custom-table entitlements before designing the schema. This primarily addresses Licensing and custom table entitlement, not the specific Scoped app lifecycle planning decision. Here, application fit also includes operational ownership and promotion practices.
B:Treat a working personal developer instance as automatic production approval. This is an unsafe or ineffective shortcut for Scoped app lifecycle planning. A proof of concept that bypasses release gates can introduce unreviewed artifacts.
D:Evaluate existing ServiceNow capabilities before building a new scoped application. This primarily addresses Reuse standard capabilities versus bespoke application, not the specific Scoped app lifecycle planning decision. Here, application fit also includes operational ownership and promotion practices.
Question 33
A developer needs a maintained REST integration rather than raw URL string concatenation. Which practical correction or implementation decision is MOST directly appropriate?
- Treat an HTML form action as a fully configured authenticated outbound REST integration.
- Configure and test the outbound REST request using approved endpoints.
- Check status, handle errors and parse expected response fields.
- Correlate requests and check the external transaction before retrying.
Explanation
Correct Answer
B:Configure and test the outbound REST request using approved endpoints. The intended behavior can be checked because a controlled test shows the expected HTTP request and provider response.
Incorrect Answers
A:Treat an HTML form action as a fully configured authenticated outbound REST integration. This would not correct the Outbound REST Message configuration workflow. Unchecked URLs and method choices can send confidential data to unintended destinations.
C:Check status, handle errors and parse expected response fields. This could help RESTMessageV2 execution and response, but it does not resolve the Outbound REST Message configuration case. ServiceNow REST messages describe external HTTP operations used by app integrations.
D:Correlate requests and check the external transaction before retrying. This could help REST timeout and retry safety, but it does not resolve the Outbound REST Message configuration case. ServiceNow REST messages describe external HTTP operations used by app integrations.
Question 34
A developer wants to automate obvious field mapping without losing renamed columns. Testing exposes this failure: Unexamined auto mapping can omit fields whose source names differ. Which remediation should be applied FIRST?
- Mark a suitable unique field map as Coalesce and validate key uniqueness.
- Assume Auto Map Matching Fields infers every foreign-key and unit conversion automatically.
- Use a tested Transform Map field script or transform script for the necessary conversion.
- Validate mapping outputs with realistic records and handle exceptions.
Explanation
Correct Answer
D:Validate mapping outputs with realistic records and handle exceptions. Confirmation requires seeing that direct name matches map and remaining fields receive reviewed explicit maps.
Incorrect Answers
A:Mark a suitable unique field map as Coalesce and validate key uniqueness. It addresses Coalesce for update versus insert, not the diagnosed Auto Map Matching Fields limits failure. Unexamined auto mapping can omit fields whose source names differ.
B:Assume Auto Map Matching Fields infers every foreign-key and unit conversion automatically. This retains the Auto Map Matching Fields limits problem. Auto-map assists matching field names but cannot infer every semantic transformation.
C:Use a tested Transform Map field script or transform script for the necessary conversion. It addresses Transform scripts for calculated mappings, not the diagnosed Auto Map Matching Fields limits failure. Unexamined auto mapping can omit fields whose source names differ.
Question 35
A development team needs an external API to reject invalid input types cleanly. Which practical correction or implementation decision is MOST directly appropriate?
- Assume any JSON-shaped object is valid for any HTTP endpoint.
- Record masked diagnostics and examine the failing endpoint and method.
- Test valid and invalid bodies against a safe sandbox endpoint.
- Configure and test the outbound REST request using approved endpoints.
Explanation
Correct Answer
C:Test valid and invalid bodies against a safe sandbox endpoint. The intended behavior can be checked because contract tests confirm correct payload types and meaningful error handling.
Incorrect Answers
A:Assume any JSON-shaped object is valid for any HTTP endpoint. This would not correct the REST endpoint and payload validation workflow. Sending malformed JSON or wrong verbs produces rejected or incorrect requests.
B:Record masked diagnostics and examine the failing endpoint and method. This could help REST logging and diagnostics, but it does not resolve the REST endpoint and payload validation case. REST integrations depend on endpoint, method, headers and payload schema.
D:Configure and test the outbound REST request using approved endpoints. This could help Outbound REST Message configuration, but it does not resolve the REST endpoint and payload validation case. REST integrations depend on endpoint, method, headers and payload schema.
Question 36
A server-side action calls an external REST service and must inspect success. If the relevant RESTMessageV2 execution and response safeguard is omitted, which outcome is the MOST directly associated failure?
- Logging Authorization headers unredacted can expose credentials.
- Assuming every network call succeeds can silently lose changes.
- Blind text conversion can silently assign invalid status or reference values.
- Unchecked URLs and method choices can send confidential data to unintended destinations.
Explanation
Correct Answer
B:Assuming every network call succeeds can silently lose changes. RESTMessageV2 performs server-side outbound requests and returns a response object. The corrective approach is to check status, handle errors and parse expected response fields.
Incorrect Answers
A:Logging Authorization headers unredacted can expose credentials. This failure pattern belongs chiefly to REST logging and diagnostics; it is not the failure most directly tested in the RESTMessageV2 execution and response situation. Assuming every network call succeeds can silently lose changes.
C:Blind text conversion can silently assign invalid status or reference values. This failure pattern belongs chiefly to Transform scripts for calculated mappings; it is not the failure most directly tested in the RESTMessageV2 execution and response situation. Assuming every network call succeeds can silently lose changes.
D:Unchecked URLs and method choices can send confidential data to unintended destinations. This failure pattern belongs chiefly to Outbound REST Message configuration; it is not the failure most directly tested in the RESTMessageV2 execution and response situation. Assuming every network call succeeds can silently lose changes.
Question 37
An imported source provides a full name but the target needs normalized components. Which approach BEST meets the requirement while respecting the system constraints?
- Create an appropriate file data source and load rows to an import set staging table.
- Apply controlled transform validation such as an onBefore script and audit skipped rows.
- Use arbitrary JavaScript in the CSV file itself and trust it as transform policy.
- Use a tested Transform Map field script or transform script for the necessary conversion.
Explanation
Correct Answer
D:Use a tested Transform Map field script or transform script for the necessary conversion. Transform scripts allow custom mapping logic where declarative mapping is insufficient. Verification should demonstrate that target fields contain correct normalized values and invalid inputs are flagged.
Incorrect Answers
A:Create an appropriate file data source and load rows to an import set staging table. This primarily addresses CSV file data source and import set, not the specific Transform scripts for calculated mappings decision. Here, transform scripts allow custom mapping logic where declarative mapping is insufficient.
B:Apply controlled transform validation such as an onBefore script and audit skipped rows. This primarily addresses Import reconciliation and onBefore rejection, not the specific Transform scripts for calculated mappings decision. Here, transform scripts allow custom mapping logic where declarative mapping is insufficient.
C:Use arbitrary JavaScript in the CSV file itself and trust it as transform policy. This is an unsafe or ineffective shortcut for Transform scripts for calculated mappings. Blind text conversion can silently assign invalid status or reference values.
Question 38
A nontechnical employee needs a simplified intake form that creates a maintenance case. After the recommended Record Producer creates app record change is implemented, which observation MOST directly verifies that it works?
- Submitting the producer creates a correctly populated target record.
- The created record contains the correct requester and asset references.
- Multiple callers get consistent results with one maintained implementation.
- Eligible users create appropriate records while unauthorized create and read attempts fail.
Explanation
Correct Answer
A:Submitting the producer creates a correctly populated target record. This directly tests whether the Record Producer creates app record goal was met. Record Producers provide a simplified record-creation interface for specified tables.
Incorrect Answers
B:The created record contains the correct requester and asset references. This is evidence about Producer variable mapping, not direct proof of the required Record Producer creates app record behavior. The relevant check is that submitting the producer creates a correctly populated target record.
C:Multiple callers get consistent results with one maintained implementation. This is evidence about Script Include utility reuse, not direct proof of the required Record Producer creates app record behavior. The relevant check is that submitting the producer creates a correctly populated target record.
D:Eligible users create appropriate records while unauthorized create and read attempts fail. This is evidence about Record producer access and audience, not direct proof of the required Record Producer creates app record behavior. The relevant check is that submitting the producer creates a correctly populated target record.
Question 39
A new scoped app contains many lists but users cannot find them in the navigator. A reviewer proposes this shortcut: Add a new database table and assume its menu automatically has all desired modules. Which principle BEST explains why a different solution is needed?
- Application menus organize navigation entries rather than storing business data.
- Modules can provide distinct navigation actions for creating versus listing records.
- Navigation visibility and table access are separate security concerns.
- Reference fields model relationships using a target table rather than ordinary unvalidated text.
Explanation
Correct Answer
A:Application menus organize navigation entries rather than storing business data. The appropriate approach is to create or configure an application menu with the intended modules.
Incorrect Answers
B:Modules can provide distinct navigation actions for creating versus listing records. This is about New-record module entry point, not why the proposed Application menu navigation shortcut should be rejected. A valid table alone does not guarantee the desired navigation grouping.
C:Navigation visibility and table access are separate security concerns. This is about Module and menu role visibility, not why the proposed Application menu navigation shortcut should be rejected. A valid table alone does not guarantee the desired navigation grouping.
D:Reference fields model relationships using a target table rather than ordinary unvalidated text. This is about Reference field relations, not why the proposed Application menu navigation shortcut should be rejected. A valid table alone does not guarantee the desired navigation grouping.
Question 40
A script writes an audit record and needs a durable reference to the acting user. If the relevant gs.getUserName versus sys_id safeguard is omitted, which outcome is the MOST directly associated failure?
- Displaying a success message before verifying the write can conceal failure.
- UI hiding alone leaves alternate access paths unprotected.
- Names may change or be duplicated and are poor ownership keys.
- Treating a free-form group name as membership proof bypasses authorization.
Explanation
Correct Answer
C:Names may change or be duplicated and are poor ownership keys. Human-readable names and stable internal record identifiers serve different purposes. The corrective approach is to use the correct server identity representation for each field.
Incorrect Answers
A:Displaying a success message before verifying the write can conceal failure. This failure pattern belongs chiefly to gs.addInfoMessage user feedback; it is not the failure most directly tested in the gs.getUserName versus sys_id situation. Names may change or be duplicated and are poor ownership keys.
B:UI hiding alone leaves alternate access paths unprotected. This failure pattern belongs chiefly to Distinguish module access from record roles; it is not the failure most directly tested in the gs.getUserName versus sys_id situation. Names may change or be duplicated and are poor ownership keys.
D:Treating a free-form group name as membership proof bypasses authorization. This failure pattern belongs chiefly to gs.getUser().isMemberOf group membership; it is not the failure most directly tested in the gs.getUserName versus sys_id situation. Names may change or be duplicated and are poor ownership keys.
