CRT-403 practice question 15 of 35

DreamHouse Realty wants to make sure an Opportunity has a field Expected_Close_Date_c populated before it is allowed to enter the qualified stage. How should an app builder solution this request?

Full set: 291 questions
Answer options
A: Record Type
B: Validation Rule Correct answer
C: Activity History
D: Page Layout
Correct Answer:
B. Validation Rule
Explanation

A validation rule is the ideal solution for this requirement. Validation rules verify that the data a user enters in a record meets specified standards before the record can be saved. An app builder can create a formula that checks if the StageName is 'Qualified' and if the ExpectedCloseDatec field is blank (ISBLANK). If both conditions are true, the rule triggers, preventing the user from saving the record and displaying a custom error message, thus enforcing the business logic.

Why Incorrect

A. Record Type: Record Types determine which business processes, page layouts, and picklist values are available, but they cannot enforce conditional field requirements based on another field's value.
C. Activity History: Activity History is a related list that displays completed tasks, logged calls, and past events. It is used for tracking engagement and has no data validation capabilities.
D. Page Layout: While a field can be made universally required on a page layout, this setting cannot be applied conditionally based on the value of another field, such as the Opportunity Stage.

References

1. Salesforce Help Documentation, "Validation Rules": "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record... For example, you can ensure that all phone number fields contain a specific format or that discounts over a certain amount require approval from a manager." This document establishes the primary function of validation rules for enforcing data integrity.

2. Salesforce Help Documentation, "Examples of Validation Rules": This page provides numerous examples. A relevant example under the "Opportunity Management" section is "Ensure that users can't change an opportunity's close date to a day in the past." The formula CloseDate < TODAY() demonstrates using a formula to check a date field's value before saving, which is analogous to the question's requirement. The logic for the question would be AND(ISPICKVAL(StageName, "Qualified"), ISBLANK(ExpectedCloseDatec)).

3. Salesforce Help Documentation, "Page Layouts": This document explains how to customize page layouts, including setting field properties. It states, "You can make a field required or read-only." This property applies to the field across the entire page layout, not conditionally.

4. Salesforce Help Documentation, "Record Types": "Record types let you offer different business processes, picklist values, and page layouts to different users." This confirms that record types are for tailoring the user experience and process, not for granular, conditional field validation during a record save.

Scroll to Top