If a business rule exists in the parent domain and a separate non-overriding business rule exists in the child domain, which rule will run for the child domain?

In a domain-separated ServiceNow instance, child domains inherit configurations and processes, including business rules, from their parent domains. When a business rule exists in a parent domain and a separate, non-overriding business rule is created in a child domain for the same table, the system's behavior is additive. Both business rules will be triggered and executed for records within the child domain, provided their respective conditions are met. The parent domain's rule typically runs first, followed by the child domain's rule, allowing for layered business logic across the domain hierarchy.

A. The parent rule will run: This is incorrect because the child domain's own separate business rules are also active and will execute in addition to the inherited parent rule.
C. The child rule will run: This describes the behavior when a child domain rule is configured to explicitly override a parent domain rule. The question specifies a "non-overriding" rule.
D. Neither rule will run: This is incorrect. Unless their conditions are not met or they are inactive, both rules are in scope for the child domain and will execute.

1. ServiceNow Product Documentation: Override a business rule for a domain. In the "Results" section, the documentation explicitly states: "If you do not override the business rule, both the parent business rule and the child business rule run." This directly confirms the additive nature of non-overriding rules.

2. ServiceNow Product Documentation: Domain separation business rules. This document explains the fundamental principle: "By default, business rules in a parent domain apply to all child domains." This establishes the basis of inheritance, which is then supplemented by any rules created directly in the child domain.