ADM-201 · Question #81
At Universal Containers, if an account is consistently late or defaults on payments, users should be prevented from creating new opportunities for that account. The administrator has created a custom
The correct answer is A. Create a validation rule on Opportunities.. To prevent users from creating new Opportunities for accounts marked with Account_Credit_Alert__c, an administrator should create a validation rule on the Opportunity object.
Question
At Universal Containers, if an account is consistently late or defaults on payments, users should be prevented from creating new opportunities for that account. The administrator has created a custom checkbox called Account_Credit_Alert__c on the Account object. What should the administrator do to prevent new Opportunities from being created if the Account_Credit_Alert__c checkbox is checked?
Options
- ACreate a validation rule on Opportunities.
- BCreate a cross-object formula on Accounts.
- CCreate a Process Builder and a field update on Opportunities.
- DCreate a criteria-based sharing rule on Accounts.
How the community answered
(33 responses)- A73% (24)
- B9% (3)
- C15% (5)
- D3% (1)
Why each option
To prevent users from creating new Opportunities for accounts marked with `Account_Credit_Alert__c`, an administrator should create a validation rule on the Opportunity object.
A validation rule on the Opportunity object can check a condition on its parent Account (`Account_Credit_Alert__c`). If the checkbox on the Account is true, the validation rule can trigger an error message, preventing the user from saving the new Opportunity record.
A cross-object formula field on Accounts can display information from related records or calculate values but cannot prevent the creation of new related Opportunity records.
Process Builder or Flow can automate actions and updates but is not designed to directly *prevent* a record from being saved at the point of creation due to a violation; validation rules are specifically for this purpose.
A criteria-based sharing rule controls record visibility and access, not the ability to create new related records.
Concept tested: Using cross-object validation rules to prevent record creation
Source: https://help.salesforce.com/s/articleView?id=sf.validation_rules_example_cross_object.htm&type=5
Topics
Community Discussion
No community discussion yet for this question.