100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 20
In the scoped Approval Automation app handling request lifecycle, a flow should start when an approval request changes to Ready but runs on unrelated edits. Select THREE complementary measures or outcomes that address this case.
- Use a form label as the trigger condition
- Only qualifying status changes start a new flow execution
- Test updates that change other fields and repeat saves
- Run the flow on every record update
- Trigger on table creation only
- Set the appropriate record trigger and filter conditions for Ready transitions
Explanation
Correct Answers
B:Set the appropriate record trigger and filter conditions for Ready transitions. This is the direct observed result required before acceptance.
C:Test updates that change other fields and repeat saves. It guards against the recurring issue: Record-trigger conditions must identify the relevant record transition or state.
F:Set the appropriate record trigger and filter conditions for Ready transitions. The diagnosed cause is: Record-trigger conditions must identify the relevant record transition or state.
Incorrect Answers
A:“Use a form label as the trigger condition” would leave this failure unresolved: Record-trigger conditions must identify the relevant record transition or state.
D:“Run the flow on every record update” would leave this failure unresolved: Record-trigger conditions must identify the relevant record transition or state.
E:“Trigger on table creation only” would leave this failure unresolved: Record-trigger conditions must identify the relevant record transition or state.
Question 21
In the scoped Vendor Onboarding app handling supplier qualification, a weekly CSV import creates duplicate supplier requests every time the same export is loaded. What is the most appropriate supported design or corrective action?
- Add more columns without any key
- Use the import filename as the target record identity
- Define a stable coalesce field mapping on the Transform Map for the intended unique identifier
- Turn off duplicate alerts and ignore repeated records
Explanation
Correct Answer
C:Define a stable coalesce field mapping on the Transform Map for the intended unique identifier. The reason is that imports without a coalesce key insert new target rows even when business records already exist.
Incorrect Answers
A:“Add more columns without any key” would leave the failure unresolved: Imports without a coalesce key insert new target rows even when business records already exist.
B:“Use the import filename as the target record identity” would leave the failure unresolved: Imports without a coalesce key insert new target rows even when business records already exist.
D:“Turn off duplicate alerts and ignore repeated records” would leave the failure unresolved: Imports without a coalesce key insert new target rows even when business records already exist.
Question 22
In the scoped Vendor Onboarding app handling supplier qualification, a weekly CSV import creates duplicate supplier requests every time the same export is loaded. Which explanation best identifies the underlying ServiceNow application-development problem?
- Rate limiting requires bounded backoff and handling of remote throttling instructions; existing partner record synchronization also require backward-compatible behavior
- Hard-coded credentials in application source are exposed through version control and code reviews; existing partner record synchronization also require backward-compatible behavior
- Imports without a coalesce key insert new target rows even when business records already exist
- Integration endpoints and payloads require trusted configuration and least-privilege access
Explanation
Correct Answer
C:Define a stable coalesce field mapping on the Transform Map for the intended unique identifier. The underlying issue is that imports without a coalesce key insert new target rows even when business records already exist.
Incorrect Answers
A: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.
B: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 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 explain the failure here.
D:This explanation belongs to another app case: In the scoped Partner Integrations app handling external data exchange, an integration posts customer data to an external endpoint over REST without verifying the approved destination and authorization scope. It does not explain the failure here.
Question 23
In the scoped Vendor Onboarding app handling supplier qualification, a weekly CSV import creates duplicate supplier requests every time the same export is loaded. After the proposed fix, which observation best proves the requirement was met?
- The integration authenticates while the committed source contains no live credentials
- A forced timeout leads to one logical partner update rather than duplicates for both old and new partner record synchronization records
- Reimporting the same source updates existing records instead of duplicating them
- Load tests show calls recover without repeated bursts or infinite retries
Explanation
Correct Answer
C:Reimporting the same source updates existing records instead of duplicating them. This verifies the effect of define a stable coalesce field mapping on the Transform Map for the intended unique identifier.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 5.1 requirement.
B:This test would assess another concern: 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 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 call returns HTTP 429 but the app retries immediately in a tight loop. It does not verify the stated 5.1 requirement.
Question 24
In the scoped Vendor Onboarding app handling supplier qualification, a weekly CSV import creates duplicate supplier requests every time the same export is loaded. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Rotate leaked secrets and restrict integration credential scope
- Record integration data classification and endpoint-change approvals and keep a rollback plan for the Integration Reviews release
- Define timeouts, retry thresholds and reconciliation policy
- Test repeat imports and unique identifier quality
Explanation
Correct Answer
D:Test repeat imports and unique identifier quality. It prevents the following recurring problem: Imports without a coalesce key insert new target rows even when business records already exist.
Incorrect Answers
A: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.
B:That safeguard addresses a different application case: 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 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 update sometimes times out after the partner has already processed the request. It does not control the cause here.
Question 25
In the scoped Vendor Onboarding app handling supplier qualification, a weekly CSV import creates duplicate supplier requests every time the same export is loaded. Select TWO complementary measures or outcomes that address this case.
- Define a stable coalesce field mapping on the Transform Map for the intended unique identifier
- Reimporting the same source updates existing records instead of duplicating them
- Add more columns without any key
- Use the import filename as the target record identity
- Turn off duplicate alerts and ignore repeated records
Explanation
Correct Answers
A:Define a stable coalesce field mapping on the Transform Map for the intended unique identifier. The diagnosed cause is: Imports without a coalesce key insert new target rows even when business records already exist.
B:Define a stable coalesce field mapping on the Transform Map for the intended unique identifier. This is the direct observed result required before acceptance.
Incorrect Answers
C:“Add more columns without any key” would leave this failure unresolved: Imports without a coalesce key insert new target rows even when business records already exist.
D:“Use the import filename as the target record identity” would leave this failure unresolved: Imports without a coalesce key insert new target rows even when business records already exist.
E:“Turn off duplicate alerts and ignore repeated records” would leave this failure unresolved: Imports without a coalesce key insert new target rows even when business records already exist.
Question 26
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. What is the most appropriate supported design or corrective action?
- Assume saving a form publishes it everywhere
- Publish an approved application version to the application repository and install it in the target test instance
- Skip version notes because this is a custom app
- Copy code manually into production scripts
Explanation
Correct Answer
B:Publish an approved application version to the application repository and install it in the target test instance. The reason is that development-state changes are not automatically a versioned deployment to other instances.
Incorrect Answers
A:“Assume saving a form publishes it everywhere” would leave the failure unresolved: Development-state changes are not automatically a versioned deployment to other instances.
C:“Skip version notes because this is a custom app” would leave the failure unresolved: Development-state changes are not automatically a versioned deployment to other instances.
D:“Copy code manually into production scripts” would leave the failure unresolved: Development-state changes are not automatically a versioned deployment to other instances.
Question 27
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Time-bounded delegation requires revocation and least privilege; existing permit requests also require backward-compatible behavior
- Source control supports version history but still requires disciplined change and review workflows
- Parallel source edits require change detection, merge review and conflict resolution; existing planned outages also require backward-compatible behavior
- Development-state changes are not automatically a versioned deployment to other instances
Explanation
Correct Answer
D:Publish an approved application version to the application repository and install it in the target test instance. The underlying issue is that development-state changes are not automatically a versioned deployment to other instances.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Work Permit Intake app used for permit requests, a contractor's delegated development access remains enabled after the delivery engagement ends. Previously created permit requests records must remain valid after the change. It does not explain the failure here.
B:This explanation belongs to another app case: In the scoped App Release Engineering app handling source-code changes, an app is linked to Git but developers edit directly on the same production branch without reviewing changes. It does not explain the failure here.
C:This explanation belongs to another app case: During a change review of the scoped Maintenance Windows app used for planned outages, two contributors independently change the same Script Include and one silently overwrites the other's work. Previously created planned outages records must remain valid after the change. It does not explain the failure here.
Question 28
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. After the proposed fix, which observation best proves the requirement was met?
- The former contractor cannot modify app files or protected resources for both old and new permit requests records
- The target instance receives the intended version and its source revision is traceable
- The target instance installs the intended version without unexpected source edits
- Both intended behaviors survive in the final reviewed source revision
Explanation
Correct Answer
C:The target instance installs the intended version without unexpected source edits. This verifies the effect of publish an approved application version to the application repository and install it in the target test instance.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Work Permit Intake app used for permit requests, a contractor's delegated development access remains enabled after the delivery engagement ends. Previously created permit requests records must remain valid after the change. It does not verify the stated 6.1 requirement.
B:This test would assess another concern: 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 verify the stated 6.1 requirement.
D:This test would assess another concern: In the scoped Office Relocation app handling move requests, two contributors independently change the same Script Include and one silently overwrites the other's work. It does not verify the stated 6.1 requirement.
Question 29
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Audit delegated developer assignments and review expiry or role removal
- Require review and test promotion before production installation
- Review delegated access after contract and personnel changes and keep a rollback plan for the Work Permit Intake release
- Use pull/compare and code-review controls for shared files
Explanation
Correct Answer
B:Require review and test promotion before production installation. It prevents the following recurring problem: Development-state changes are not automatically a versioned deployment to other instances.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Field Safety app handling site-inspection records, a developer without the admin role needs to edit only one scoped application. It does not control the cause here.
C:That safeguard addresses a different application case: During a change review of the scoped Work Permit Intake app used for permit requests, a contractor's delegated development access remains enabled after the delivery engagement ends. Previously created permit requests records must remain valid after the change. It does not control the cause here.
D:That safeguard addresses a different application case: In the scoped Office Relocation app handling move requests, two contributors independently change the same Script Include and one silently overwrites the other's work. It does not control the cause here.
Question 30
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. Select THREE complementary measures or outcomes that address this case.
- Require review and test promotion before production installation
- The target instance installs the intended version without unexpected source edits
- Skip version notes because this is a custom app
- Assume saving a form publishes it everywhere
- Publish an approved application version to the application repository and install it in the target test instance
- Copy code manually into production scripts
Explanation
Correct Answers
A:Require review and test promotion before production installation. It guards against the recurring issue: Development-state changes are not automatically a versioned deployment to other instances.
B:Publish an approved application version to the application repository and install it in the target test instance. This is the direct observed result required before acceptance.
E:Publish an approved application version to the application repository and install it in the target test instance. The diagnosed cause is: Development-state changes are not automatically a versioned deployment to other instances.
Incorrect Answers
C:“Skip version notes because this is a custom app” would leave this failure unresolved: Development-state changes are not automatically a versioned deployment to other instances.
D:“Assume saving a form publishes it everywhere” would leave this failure unresolved: Development-state changes are not automatically a versioned deployment to other instances.
F:“Copy code manually into production scripts” would leave this failure unresolved: Development-state changes are not automatically a versioned deployment to other instances.
ServiceNow Certified Application Developer (CAD) Practice Tests