Professional Documents
Culture Documents
1) In task record watch list users added to it will receive notification of anything added to
work notes
Ans – No
Ans -Used for filtering the records (Don’t remember other options)
14) In user menu what actions can user complete?
15) Purpose of update set? (Please choose the option carefully as answers are tricky)
Ans – Customizations involving movement of update set from prod to development.
Ans -Event causes a trigger which has a direct response in service now
Ans -Breadcrumbs.
19) What role is used for adding or removing fields from the list?
Ans -Personalize_list.
20) Task related records extend task table. Can a task refer one or more configuration
items?
Ans -True.
Ans -It should satisfy both row and field level acl’s
23) Incident number is already prefixed with INCT. Can it be changed to INC using which
option below?
Ans -Roles will contain other roles and will inherit the contained roles as well.
26) How to differentiate SLA, OLA and underpinning contracts based on which options
below?
Ans -Type.
37) To generate task based records through service request which is the correct option
below?
Ans -Record producer.
38) When submit button appears on the form?
Ans -New record.
39) Which is correct from below?
Ans -A column is field and row is a record.
40) Multiple customizations are done to the same form through different update sets.
Which change would be moved to production.
Ans – After merging the update sets the most recent one will be available.