A company has a model-driven app with a custom table 'Issue' that has a choice column 'Status' with values: New, In Progress, Resolved, Closed. The app uses a business rule to set 'Resolved By' (lookup to User) when status changes to Resolved. Users report that the 'Resolved By' field is not being populated. What is the most likely cause?
Business rules only apply to the form they are scoped to.
Why this answer
Business rules in model-driven apps can be scoped to either the entity (all forms) or a specific form. If the rule is scoped to a particular form (e.g., the main form) but the status change occurs via a quick create form, the rule will not trigger. This is the most likely cause because users report the field is not populated, indicating the rule is not firing in the context where the status is being changed.
Exam trap
The trap here is that candidates assume a business rule always applies to all forms of an entity, overlooking the scope setting that can restrict it to a specific form type, such as the main form versus a quick create form.
How to eliminate wrong answers
Option A is wrong because the 'Resolved By' lookup column not being on the form would not prevent the business rule from populating it; business rules can set field values regardless of whether the field is visible on the form. Option B is wrong because a required column would cause a validation error on save, not silently leave the field empty. Option D is wrong because if the business rule were deactivated, it would never fire in any context, but the question states users report the field is not being populated, implying it works in some scenarios (e.g., main form) but not others (quick create), which points to a scoping issue rather than deactivation.