ServiceNow CIS-SP Practice Questions

Answer: D

Why this is correct
Health Preferences calls the Active setting the most important one, because the more domains with flags set to Active, the longer the jobs take. The default for the global domain is Active = true. The page then says: if there is a large number of domains (>100) the job can take a very long time. To mitigate this, set Active to false for all the root domains, thereby disabling all the other domains in the hierarchy. If there is a rule at the top, all child domains inherit that rule. After that, only the domains you wish to be Active need to be turned back on, and users should consider the domain hierarchy when doing so.

Why the other options are wrong
"Set Active to true for all the root domains" … Active = true is what makes a domain part of the job, and the more domains are Active, the longer the jobs take. Setting it on every root domain keeps the run long.
"Set Active to false in each child domain" … The page sets the flag at the top instead: setting Active to false for the root domains disables all the other domains in the hierarchy, because child domains inherit the rule at the top.
"Raise the Failure Threshold in each domain" … Failure Threshold, Create Task, and Task Assignee Group can be set differently for each domain depending on what is needed. The setting the page ties to job duration is Active.

Key point
On an instance with many customers, start CMDB Health with every root domain inactive and enable the domains that have agreed to use it. Each domain you add makes the run longer.