What type of rule prevents saving data when the value of Headcount exceeds 1000?

• A. Groovy Rule
• B. Create a Valid intersection rule
• C. Create a Task Manager Rule
• D. Configurable Consolidation Rule

Answer: (A)

Groovy Rules are used to implement custom, dynamic data-entry validations. They let you write logic that runs as data is saved, so you can inspect the values being entered and enforce conditions that aren’t covered by standard rules. In this scenario, you can script a check like: if the Headcount value being saved is greater than 1000, raise an error to stop the save. That exact capability—evaluating a numeric condition across dimensions and blocking the save when it’s breached—is what Groovy Rules are designed for.

The other rule types don’t fit this need. A valid intersection rule governs which dimension intersections are permitted, not a runtime threshold check on a numeric field. A Task Manager rule relates to workflow and approvals, not data validation at save time. A Configurable Consolidation Rule controls how data is aggregated during consolidation, not the entry-time validation of values.