Select the recommended approach to Domain Separation

The recommended approach for a successful and maintainable Domain Separation implementation, as advised by ServiceNow, is to heavily rely on standard data separation. This model suggests that at least 80% of separation requirements should be met using the out-of-the-box sysdomain field on data records. Approximately 15% can be handled through data-driven rules, where domain assignment is automated based on record attributes (e.g., company). Critically, configuration-level separation (creating domain-specific business rules, UI policies, etc.) should be minimized to less than 5%. This strategy reduces complexity, lowers maintenance overhead, and simplifies future platform upgrades.

A. Incorrect. This model significantly understates the reliance on Standard separation (should be 80%+) and vastly overestimates the acceptable level of Configuration separation (should be <5%).
B. Incorrect. This option incorrectly prioritizes data-driven separation over Standard separation. The primary method should always be the standard, out-of-the-box functionality.
C. Incorrect. While the percentage for Configuration is correct, the recommended target for Standard separation is higher (80% or more) to ensure maximum use of the core platform feature.

1. ServiceNow Training Courseware: CIS - Domain Separation Implementation. In the "Domain Separation Architecture and Best Practices" module, ServiceNow explicitly presents the "80/15/5" rule as the target model for implementation: 80% or more Standard data separation, 15% or more data-driven separation, and less than 5% configuration/process separation.

2. ServiceNow Product Documentation: Domain separation best practices. While the documentation does not state the exact percentages, it strongly reinforces the principle behind them: "Avoid creating domain-specific configurations unless absolutely necessary... Over-configuration can lead to performance issues and upgrade difficulties." This supports minimizing the configuration percentage to the lowest possible value, as reflected in option D. (ServiceNow Product Documentation, Quebec release, "Domain separation best practices" section).

3. ServiceNow White Paper: A Guide to Implementing Domain Separation. This guide emphasizes that the goal of domain separation is data segregation, not creating distinct application logic for each domain. It states, "The key to a successful Domain Separation implementation is to keep it simple... Limit the amount of domain-specific customization." This aligns with the 80/15/5 model where customization (configuration) is kept below 5%.