100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 380
In the scoped Approval Automation app handling request lifecycle, a subflow receives a record sys_id but a calling flow cannot use its calculated decision afterward. Select THREE complementary measures or outcomes that address this case.
- Turn the result into a static annotation
- Contract-test the subflow against all calling flows
- Define the subflow output and assign it before completion
- Put the result in an invisible form field only
- Assume every local variable becomes an output automatically
- The calling flow receives the expected decision data pill
Explanation
Correct Answers
B:Contract-test the subflow against all calling flows. It guards against the recurring issue: Reusable subflows need declared inputs and outputs for data exchange.
C:Define the subflow output and assign it before completion. The diagnosed cause is: Reusable subflows need declared inputs and outputs for data exchange.
F:Define the subflow output and assign it before completion. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Turn the result into a static annotation” would leave this failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
D:“Put the result in an invisible form field only” would leave this failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
E:“Assume every local variable becomes an output automatically” would leave this failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
Question 381
In the scoped Data Imports app handling scheduled import batches, a team loads CSV directly into a production custom table, bypassing reconciliation and duplicate review. What is the most appropriate supported design or corrective action?
- Use an Import Set staging process and a reviewed Transform Map
- Copy the CSV into table cells manually
- Skip staging because it is an internal file
- Assume row totals prove accurate field mapping
Explanation
Correct Answer
A:Use an Import Set staging process and a reviewed Transform Map. The reason is that staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
Incorrect Answers
B:“Copy the CSV into table cells manually” would leave the failure unresolved: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
C:“Skip staging because it is an internal file” would leave the failure unresolved: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
D:“Assume row totals prove accurate field mapping” would leave the failure unresolved: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
Question 382
In the scoped Data Imports app handling scheduled import batches, a team loads CSV directly into a production custom table, bypassing reconciliation and duplicate review. Which explanation best identifies the underlying ServiceNow application-development problem?
- Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports
- Hard-coded credentials in application source are exposed through version control and code reviews
- Rate limiting requires bounded backoff and handling of remote throttling instructions; existing partner record synchronization also require backward-compatible behavior
- Network timeouts can leave external side-effect outcome ambiguous; existing partner record synchronization also require backward-compatible behavior
Explanation
Correct Answer
A:Use an Import Set staging process and a reviewed Transform Map. The underlying issue is that staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
Incorrect Answers
B:This explanation belongs to another app case: In the scoped Partner Integrations app handling external data exchange, an outbound REST integration stores a partner API password in a shared Script Include source file. It does not explain the failure here.
C:This explanation belongs to another app case: During a change review of the scoped Integration Reviews app used for partner record synchronization, a REST call returns HTTP 429 but the app retries immediately in a tight loop. Previously created partner record synchronization records must remain valid after the change. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Integration Reviews app used for partner record synchronization, an outbound REST update sometimes times out after the partner has already processed the request. Previously created partner record synchronization records must remain valid after the change. It does not explain the failure here.
Question 383
In the scoped Data Imports app handling scheduled import batches, a team loads CSV directly into a production custom table, bypassing reconciliation and duplicate review. After the proposed fix, which observation best proves the requirement was met?
- Only the authorized destination receives the permitted fields for both old and new partner record synchronization records
- Target counts and field values reconcile to the reviewed source batch
- The integration authenticates while the committed source contains no live credentials for both old and new partner record synchronization records
- Incomplete responses are rejected without corrupting target records
Explanation
Correct Answer
B:Target counts and field values reconcile to the reviewed source batch. This verifies the effect of use an Import Set staging process and a reviewed Transform Map.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Integration Reviews app used for partner record synchronization, an integration posts customer data to an external endpoint over REST without verifying the approved destination and authorization scope. Previously created partner record synchronization records must remain valid after the change. It does not verify the stated 5.1 requirement.
C:This test would assess another concern: During a change review of the scoped Integration Reviews app used for partner record synchronization, an outbound REST integration stores a partner API password in a shared Script Include source file. Previously created partner record synchronization records must remain valid after the change. It does not verify the stated 5.1 requirement.
D:This test would assess another concern: In the scoped Partner Integrations app handling external data exchange, a REST integration receives HTTP 200 with a JSON body missing the required account identifier. It does not verify the stated 5.1 requirement.
Question 384
In the scoped Data Imports app handling scheduled import batches, a team loads CSV directly into a production custom table, bypassing reconciliation and duplicate review. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test valid, missing-field and unexpected-shape responses and keep a rollback plan for the Integration Reviews release
- Monitor response status and partner API limits
- Rotate leaked secrets and restrict integration credential scope
- Keep row-level error reports and rollback criteria
Explanation
Correct Answer
D:Keep row-level error reports and rollback criteria. It prevents the following recurring problem: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Integration Reviews app used for partner record synchronization, a REST integration receives HTTP 200 with a JSON body missing the required account identifier. Previously created partner record synchronization records must remain valid after the change. It does not control the cause here.
B:That safeguard addresses a different application case: In the scoped Partner Integrations app handling external data exchange, a REST call returns HTTP 429 but the app retries immediately in a tight loop. It does not control the cause here.
C:That safeguard addresses a different application case: In the scoped Partner Integrations app handling external data exchange, an outbound REST integration stores a partner API password in a shared Script Include source file. It does not control the cause here.
Question 385
In the scoped Data Imports app handling scheduled import batches, a team loads CSV directly into a production custom table, bypassing reconciliation and duplicate review. Select TWO complementary measures or outcomes that address this case.
- Target counts and field values reconcile to the reviewed source batch
- Use an Import Set staging process and a reviewed Transform Map
- Copy the CSV into table cells manually
- Skip staging because it is an internal file
- Assume row totals prove accurate field mapping
Explanation
Correct Answers
A:Use an Import Set staging process and a reviewed Transform Map. This is the direct observed result required before acceptance.
B:Use an Import Set staging process and a reviewed Transform Map. The diagnosed cause is: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
Incorrect Answers
C:“Copy the CSV into table cells manually” would leave this failure unresolved: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
D:“Skip staging because it is an internal file” would leave this failure unresolved: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
E:“Assume row totals prove accurate field mapping” would leave this failure unresolved: Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports.
Question 386
In the scoped Lab Reservations app handling instrument bookings, a contractor's delegated development access remains enabled after the delivery engagement ends. What is the most appropriate supported design or corrective action?
- Leave access indefinitely as a convenience
- Remove the contractor's delegated developer assignment when the approved work ends
- Rely on lack of navigation visibility as revocation
- Rename the contractor display name to revoke access
Explanation
Correct Answer
B:Remove the contractor's delegated developer assignment when the approved work ends. The reason is that time-bounded delegation requires revocation and least privilege.
Incorrect Answers
A:“Leave access indefinitely as a convenience” would leave the failure unresolved: Time-bounded delegation requires revocation and least privilege.
C:“Rely on lack of navigation visibility as revocation” would leave the failure unresolved: Time-bounded delegation requires revocation and least privilege.
D:“Rename the contractor display name to revoke access” would leave the failure unresolved: Time-bounded delegation requires revocation and least privilege.
Question 387
In the scoped Lab Reservations app handling instrument bookings, a contractor's delegated development access remains enabled after the delivery engagement ends. Which explanation best identifies the underlying ServiceNow application-development problem?
- Time-bounded delegation requires revocation and least privilege
- Development-state changes are not automatically a versioned deployment to other instances; existing review evidence also require backward-compatible behavior
- The organization application repository and public Store distribution are distinct processes
- Source control supports version history but still requires disciplined change and review workflows; existing tested application releases also require backward-compatible behavior
Explanation
Correct Answer
A:Remove the contractor's delegated developer assignment when the approved work ends. The underlying issue is that time-bounded delegation requires revocation and least privilege.
Incorrect Answers
B:This explanation belongs to another app case: During a change review of the scoped Application Audits app used for review evidence, a developer finishes a scoped app but expects production to receive it automatically after saving in Studio. Previously created review evidence records must remain valid after the change. It does not explain the failure here.
C:This explanation belongs to another app case: In the scoped App Release Engineering app handling source-code changes, a team expects an application published to the organization repository to become public in the ServiceNow Store. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped App Deployment app used for tested application releases, an app is linked to Git but developers edit directly on the same production branch without reviewing changes. Previously created tested application releases records must remain valid after the change. It does not explain the failure here.
Question 388
In the scoped Lab Reservations app handling instrument bookings, a contractor's delegated development access remains enabled after the delivery engagement ends. After the proposed fix, which observation best proves the requirement was met?
- The target instance installs the intended version without unexpected source edits
- The former contractor cannot modify app files or protected resources
- Both test environments report the expected application version and behavior
- The app is available only to intended organization instances and remains non-public
Explanation
Correct Answer
B:The former contractor cannot modify app files or protected resources. This verifies the effect of remove the contractor's delegated developer assignment when the approved work ends.
Incorrect Answers
A:This test would assess another concern: In the scoped Security Exceptions app handling risk acknowledgments, a developer finishes a scoped app but expects production to receive it automatically after saving in Studio. It does not verify the stated 6.2 requirement.
C:This test would assess another concern: In the scoped App Release Engineering app handling source-code changes, two target instances show different app behavior because one remains on an earlier repository version. It does not verify the stated 6.2 requirement.
D:This test would assess another concern: In the scoped App Release Engineering app handling source-code changes, a team expects an application published to the organization repository to become public in the ServiceNow Store. It does not verify the stated 6.2 requirement.
Question 389
In the scoped Lab Reservations app handling instrument bookings, a contractor's delegated development access remains enabled after the delivery engagement ends. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Require review and test promotion before production installation
- Document repository-to-release promotion and rollback evidence
- Track installed versions and regression tests per environment and keep a rollback plan for the App Deployment release
- Review delegated access after contract and personnel changes
Explanation
Correct Answer
D:Review delegated access after contract and personnel changes. It prevents the following recurring problem: Time-bounded delegation requires revocation and least privilege.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Security Exceptions app handling risk acknowledgments, a developer finishes a scoped app but expects production to receive it automatically after saving in Studio. It does not control the cause here.
B:That safeguard addresses a different application case: In the scoped App Release Engineering app handling source-code changes, a developer commits to Git but cannot explain how another instance receives the approved application release. It does not control the cause here.
C:That safeguard addresses a different application case: During a change review of the scoped App Deployment app used for tested application releases, two target instances show different app behavior because one remains on an earlier repository version. Previously created tested application releases records must remain valid after the change. It does not control the cause here.
Question 390
In the scoped Lab Reservations app handling instrument bookings, a contractor's delegated development access remains enabled after the delivery engagement ends. Select THREE complementary measures or outcomes that address this case.
- Review delegated access after contract and personnel changes
- The former contractor cannot modify app files or protected resources
- Rename the contractor display name to revoke access
- Leave access indefinitely as a convenience
- Rely on lack of navigation visibility as revocation
- Remove the contractor's delegated developer assignment when the approved work ends
Explanation
Correct Answers
A:Review delegated access after contract and personnel changes. It guards against the recurring issue: Time-bounded delegation requires revocation and least privilege.
B:Remove the contractor's delegated developer assignment when the approved work ends. This is the direct observed result required before acceptance.
F:Remove the contractor's delegated developer assignment when the approved work ends. The diagnosed cause is: Time-bounded delegation requires revocation and least privilege.
Incorrect Answers
C:“Rename the contractor display name to revoke access” would leave this failure unresolved: Time-bounded delegation requires revocation and least privilege.
D:“Leave access indefinitely as a convenience” would leave this failure unresolved: Time-bounded delegation requires revocation and least privilege.
E:“Rely on lack of navigation visibility as revocation” would leave this failure unresolved: Time-bounded delegation requires revocation and least privilege.
ServiceNow Certified Application Developer (CAD) Practice Tests