New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ServiceNow CAD Exam - Topic 5 Question 49 Discussion

Actual exam question for ServiceNow's CAD exam
Question #: 49
Topic #: 5
[All CAD Questions]

A customer requests the following data quality measures be added:

1. Incident numbers should be read-only on all lists and forms, for all users.

2. Short Description field should be mandatory, on all records, across all applications, on Insert.

Which type of policy would you use to meet this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: B

'Use an existing MID Server to connect to a Source Control repository. Linking or importing an application through a MID Server enables access to repositories behind a firewall.' https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/c_SourceControlIntegration.html


by Howard at Mar 01, 2023, 03:36 AM

Limited Time Offer

25%

Off

Get Premium CAD Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Audria
4 months ago
Not sure if a single policy can handle both requests effectively.
upvoted 0 times
...
Dierdre
4 months ago
Field Criteria Policy could also work for the mandatory field.
upvoted 0 times
...
Kenny
5 months ago
Wait, why would incident numbers need to be read-only? Seems odd.
upvoted 0 times
...
Lizbeth
5 months ago
Definitely agree with that!
upvoted 0 times
...
Sherita
5 months ago
I think a Data Quality Policy would cover both requirements.
upvoted 0 times
...
Kristal
5 months ago
I’m leaning towards Data Policy, but I’m not confident. It seems like it could cover both requirements.
upvoted 0 times
...
Ollie
5 months ago
I feel like this is similar to a practice question we did on making fields read-only. Maybe Dictionary Design Policy could be the answer?
upvoted 0 times
...
Ling
5 months ago
I'm not entirely sure, but I remember something about Field Criteria Policy being used for mandatory fields.
upvoted 0 times
...
Tran
5 months ago
I think we might need a Data Quality Policy for this since it involves ensuring data integrity across applications.
upvoted 0 times
...
Selma
5 months ago
I'm feeling pretty confident about this one. Based on my understanding of Cisco networking and Python, I think Option B is the correct answer.
upvoted 0 times
...
Nancey
5 months ago
Okay, let's see. Routers and switches have built-in monitoring capabilities, so those wouldn't require extra hardware. Hubs, on the other hand, just blindly forward traffic, so you'd need something like a network tap or port mirroring to monitor a hub-based network. I'm going with C.
upvoted 0 times
...
Alaine
5 months ago
I vaguely remember something about FreeDBStorage being relevant too, but I thought that was more related to databases rather than instances.
upvoted 0 times
...
Blondell
6 months ago
Hmm, this one seems a bit tricky. I'll need to think carefully about the model numbers and Intel's processor naming conventions.
upvoted 0 times
...
Melodie
10 months ago
As someone who's spilled coffee on their laptop during an exam, I can appreciate the need for read-only incident numbers. Wouldn't want to accidentally delete that history!
upvoted 0 times
Lindsay
9 months ago
A: And we can make the Short Description field mandatory on Insert with that policy as well.
upvoted 0 times
...
Elenore
9 months ago
B: Yeah, that sounds like the best option to ensure the incident numbers are read-only for all users.
upvoted 0 times
...
Elbert
9 months ago
A: I think we should use a Data Quality Policy to meet this requirement.
upvoted 0 times
...
...
Aleisha
10 months ago
Dictionary Design Policy? Really? That's like using a sledgehammer to crack a nut. Data Quality Policy is the way to go here.
upvoted 0 times
Micheline
10 months ago
Data Quality Policy would definitely be the most appropriate choice in this scenario.
upvoted 0 times
...
Aracelis
10 months ago
Yeah, Dictionary Design Policy seems like overkill for these data quality measures.
upvoted 0 times
...
Ty
10 months ago
I agree, Data Quality Policy is the best option for this requirement.
upvoted 0 times
...
...
Mel
11 months ago
I was leaning towards Field Criteria Policy, but the requirements span across multiple applications, so Data Quality Policy makes more sense.
upvoted 0 times
Izetta
9 months ago
Data Policy could also work, but Data Quality Policy seems more specific to the requirement.
upvoted 0 times
...
Cruz
9 months ago
Field Criteria Policy may not be sufficient for this scenario.
upvoted 0 times
...
Queen
9 months ago
I agree, it covers the requirement for all users and across all applications.
upvoted 0 times
...
Sang
9 months ago
I think Data Quality Policy would be the best choice.
upvoted 0 times
...
Providencia
9 months ago
Yes, Data Quality Policy would be the most suitable for enforcing those data quality measures across all applications.
upvoted 0 times
...
Fredric
9 months ago
Data Quality Policy definitely seems like the way to go to meet those specific requirements.
upvoted 0 times
...
Roxane
9 months ago
I agree, it seems like the most comprehensive option to ensure consistency across all applications.
upvoted 0 times
...
Herman
10 months ago
I think Data Quality Policy would be the best choice for this scenario.
upvoted 0 times
...
...
Luis
11 months ago
Data Policy seems like a good option too, but Data Quality Policy is probably more specific to these kinds of data quality measures.
upvoted 0 times
...
Pearlene
11 months ago
I think the correct answer is Data Quality Policy. It seems like the best fit to handle both read-only incident numbers and mandatory short description field requirements.
upvoted 0 times
...
Tyisha
11 months ago
I'm not sure, but I think a Data Quality Policy could also work for this scenario.
upvoted 0 times
...
Jimmie
11 months ago
I agree with Rosalind, a Field Criteria Policy would be the best choice to make those changes.
upvoted 0 times
...
Rosalind
11 months ago
I think we should use a Field Criteria Policy for this requirement.
upvoted 0 times
...

Save Cancel