100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 500
In the scoped Notification Center app handling case email messages, an administrator wants to change an application's notification lead time without editing application scripts. Select THREE complementary measures or outcomes that address this case.
- Store configuration in an unversioned client global
- Set a safe default and restrict who can modify the property
- Create a scoped application property and read it with gs.getProperty using the scoped name
- Use a form placeholder as the setting
- Hard-code the lead time in every Script Include
- Changing the approved property changes future runs without code edits
Explanation
Correct Answers
B:Set a safe default and restrict who can modify the property. It guards against the recurring issue: Configurable application properties separate tunable settings from code.
C:Create a scoped application property and read it with gs.getProperty using the scoped name. The diagnosed cause is: Configurable application properties separate tunable settings from code.
F:Create a scoped application property and read it with gs.getProperty using the scoped name. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Store configuration in an unversioned client global” would leave this failure unresolved: Configurable application properties separate tunable settings from code.
D:“Use a form placeholder as the setting” would leave this failure unresolved: Configurable application properties separate tunable settings from code.
E:“Hard-code the lead time in every Script Include” would leave this failure unresolved: Configurable application properties separate tunable settings from code.
Question 501
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. What is the most appropriate supported design or corrective action?
- Use bounded retry with suitable backoff and respect retry guidance where provided
- Remove request logging to hide failures
- Retry the request without delay forever
- Treat every 429 as a successful write
Explanation
Correct Answer
A:Use bounded retry with suitable backoff and respect retry guidance where provided. The reason is that rate limiting requires bounded backoff and handling of remote throttling instructions.
Incorrect Answers
B:“Remove request logging to hide failures” would leave the failure unresolved: Rate limiting requires bounded backoff and handling of remote throttling instructions.
C:“Retry the request without delay forever” would leave the failure unresolved: Rate limiting requires bounded backoff and handling of remote throttling instructions.
D:“Treat every 429 as a successful write” would leave the failure unresolved: Rate limiting requires bounded backoff and handling of remote throttling instructions.
Question 502
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Rate limiting requires bounded backoff and handling of remote throttling instructions
- Staging and Transform Maps provide controlled mapping and diagnostics for bulk imports
- Import transform should validate and sanitize untrusted source values for the intended field
- A source field may require type-aware mapping and transformation before writing to the target; existing incoming partner files also require backward-compatible behavior
Explanation
Correct Answer
A:Use bounded retry with suitable backoff and respect retry guidance where provided. The underlying issue is that rate limiting requires bounded backoff and handling of remote throttling instructions.
Incorrect Answers
B:This explanation belongs to another app case: 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. It does not explain the failure here.
C:This explanation belongs to another app case: In the scoped Partner Integrations app handling external data exchange, an imported data source contains untrusted HTML in a description field and the developer lets it populate public UI unrestricted. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Import Reconciliation app used for incoming partner files, a CSV column called renewal_date loads as text and becomes an invalid date on the target table. Previously created incoming partner files records must remain valid after the change. It does not explain the failure here.
Question 503
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. After the proposed fix, which observation best proves the requirement was met?
- Valid source dates become correct target dates; malformed rows produce traceable errors
- Load tests show calls recover without repeated bursts or infinite retries
- Malformed or malicious content is rejected or safely stored and displayed for both old and new partner record synchronization records
- Every required source column maps to the intended target field for both old and new review evidence records
Explanation
Correct Answer
B:Load tests show calls recover without repeated bursts or infinite retries. This verifies the effect of use bounded retry with suitable backoff and respect retry guidance where provided.
Incorrect Answers
A:This test would assess another concern: In the scoped Data Imports app handling scheduled import batches, a CSV column called renewal_date loads as text and becomes an invalid date on the target table. It does not verify the stated 5.2 requirement.
C:This test would assess another concern: During a change review of the scoped Integration Reviews app used for partner record synchronization, an imported data source contains untrusted HTML in a description field and the developer lets it populate public UI unrestricted. Previously created partner record synchronization records must remain valid after the change. It does not verify the stated 5.2 requirement.
D:This test would assess another concern: During a change review of the scoped Application Audits app used for review evidence, a finance export has column labels that differ from the target table, so automatic mapping skips required fields. Previously created review evidence records must remain valid after the change. It does not verify the stated 5.2 requirement.
Question 504
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Review collision cases and business key uniqueness
- Test repeat imports and unique identifier quality
- Monitor response status and partner API limits
- Use a source-to-target mapping matrix during import acceptance testing and keep a rollback plan for the Application Audits release
Explanation
Correct Answer
C:Monitor response status and partner API limits. It prevents the following recurring problem: Rate limiting requires bounded backoff and handling of remote throttling instructions.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Employee Services app handling staff records, a recurring import identifies an employee's multiple active licenses using only employee ID as coalesce. It does not control the cause here.
B:That safeguard addresses a different application case: In the scoped Vendor Onboarding app handling supplier qualification, a weekly CSV import creates duplicate supplier requests every time the same export is loaded. It does not control the cause here.
D:That safeguard addresses a different application case: During a change review of the scoped Application Audits app used for review evidence, a finance export has column labels that differ from the target table, so automatic mapping skips required fields. Previously created review evidence records must remain valid after the change. It does not control the cause here.
Question 505
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. Select TWO complementary measures or outcomes that address this case.
- Treat every 429 as a successful write
- Retry the request without delay forever
- Remove request logging to hide failures
- Use bounded retry with suitable backoff and respect retry guidance where provided
- Load tests show calls recover without repeated bursts or infinite retries
Explanation
Correct Answers
D:Use bounded retry with suitable backoff and respect retry guidance where provided. The diagnosed cause is: Rate limiting requires bounded backoff and handling of remote throttling instructions.
E:Use bounded retry with suitable backoff and respect retry guidance where provided. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Treat every 429 as a successful write” would leave this failure unresolved: Rate limiting requires bounded backoff and handling of remote throttling instructions.
B:“Retry the request without delay forever” would leave this failure unresolved: Rate limiting requires bounded backoff and handling of remote throttling instructions.
C:“Remove request logging to hide failures” would leave this failure unresolved: Rate limiting requires bounded backoff and handling of remote throttling instructions.
Question 506
In the scoped App Release Engineering app handling source-code changes, studio source-control link points at a different team's repository and imports unrelated application files. What is the most appropriate supported design or corrective action?
- Remove application scope to resolve conflicts
- Disable commit history to avoid confusing names
- Verify repository URL, branch and application scope before importing or committing
- Pull from the first similarly named repository
Explanation
Correct Answer
C:Verify repository URL, branch and application scope before importing or committing. The reason is that a source-control repository association must match the intended scoped application's ownership.
Incorrect Answers
A:“Remove application scope to resolve conflicts” would leave the failure unresolved: A source-control repository association must match the intended scoped application's ownership.
B:“Disable commit history to avoid confusing names” would leave the failure unresolved: A source-control repository association must match the intended scoped application's ownership.
D:“Pull from the first similarly named repository” would leave the failure unresolved: A source-control repository association must match the intended scoped application's ownership.
Question 507
In the scoped App Release Engineering app handling source-code changes, studio source-control link points at a different team's repository and imports unrelated application files. Which explanation best identifies the underlying ServiceNow application-development problem?
- The organization application repository and public Store distribution are distinct processes; existing tested application releases also require backward-compatible behavior
- Time-bounded delegation requires revocation and least privilege; existing permit requests also require backward-compatible behavior
- Delegated development grants app-level development privileges without broad system administration
- A source-control repository association must match the intended scoped application's ownership
Explanation
Correct Answer
D:Verify repository URL, branch and application scope before importing or committing. The underlying issue is that a source-control repository association must match the intended scoped application's ownership.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped App Deployment app used for tested application releases, a team expects an application published to the organization repository to become public in the ServiceNow Store. Previously created tested application releases 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 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.
C:This explanation belongs to another app 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 explain the failure here.
Question 508
In the scoped App Release Engineering app handling source-code changes, studio source-control link points at a different team's repository and imports unrelated application files. After the proposed fix, which observation best proves the requirement was met?
- The app is available only to intended organization instances and remains non-public
- Allowed development continues while protected ACL operations remain controlled for both old and new protected case records records
- A test instance can identify and recover from the failed candidate release for both old and new renewal cases records
- The linked application files match the authorized repository and target branch
Explanation
Correct Answer
D:The linked application files match the authorized repository and target branch. This verifies the effect of verify repository URL, branch and application scope before importing or committing.
Incorrect Answers
A: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.3 requirement.
B:This test would assess another concern: During a change review of the scoped Security Exceptions app used for protected case records, a delegated developer can edit some artifacts but cannot alter all security ACLs. Previously created protected case records records must remain valid after the change. It does not verify the stated 6.3 requirement.
C:This test would assess another concern: During a change review of the scoped Contract Renewals app used for renewal cases, a new application version introduces a regression and the team has no record of which artifact was installed. Previously created renewal cases records must remain valid after the change. It does not verify the stated 6.3 requirement.
Question 509
In the scoped App Release Engineering app handling source-code changes, studio source-control link points at a different team's repository and imports unrelated application files. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Track installed versions and regression tests per environment and keep a rollback plan for the App Deployment release
- Require review and test promotion before production installation
- Review repository permissions and configuration at onboarding
- Retain signed deployment decisions and compatibility checks and keep a rollback plan for the Contract Renewals release
Explanation
Correct Answer
C:Review repository permissions and configuration at onboarding. It prevents the following recurring problem: A source-control repository association must match the intended scoped application's ownership.
Incorrect Answers
A: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.
B: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.
D:That safeguard addresses a different application case: During a change review of the scoped Contract Renewals app used for renewal cases, a new application version introduces a regression and the team has no record of which artifact was installed. Previously created renewal cases records must remain valid after the change. It does not control the cause here.
Question 510
In the scoped App Release Engineering app handling source-code changes, studio source-control link points at a different team's repository and imports unrelated application files. Select THREE complementary measures or outcomes that address this case.
- Remove application scope to resolve conflicts
- Review repository permissions and configuration at onboarding
- Disable commit history to avoid confusing names
- Verify repository URL, branch and application scope before importing or committing
- Pull from the first similarly named repository
- The linked application files match the authorized repository and target branch
Explanation
Correct Answers
B:Review repository permissions and configuration at onboarding. It guards against the recurring issue: A source-control repository association must match the intended scoped application's ownership.
D:Verify repository URL, branch and application scope before importing or committing. The diagnosed cause is: A source-control repository association must match the intended scoped application's ownership.
F:Verify repository URL, branch and application scope before importing or committing. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Remove application scope to resolve conflicts” would leave this failure unresolved: A source-control repository association must match the intended scoped application's ownership.
C:“Disable commit history to avoid confusing names” would leave this failure unresolved: A source-control repository association must match the intended scoped application's ownership.
E:“Pull from the first similarly named repository” would leave this failure unresolved: A source-control repository association must match the intended scoped application's ownership.
ServiceNow Certified Application Developer (CAD) Practice Tests