Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CRT-450 Topic 6 Question 41 Discussion

Actual exam question for Salesforce's CRT-450 exam
Question #: 41
Topic #: 6
[All CRT-450 Questions]

A developer is asked to prevent anyone other than a user with Sales Manager profile from changing the Opportunity Status to Closed Lost if the lost reason is blank.

Which automation allows the developer to satisfy this requirement in the most efficient manner?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Selma
2 months ago
I don't know, guys. If the lost reason is blank, maybe the opportunity should just automatically be set to Closed Lost. No need to overthink it, am I right?
upvoted 0 times
...
Rasheeda
2 months ago
Approval process? Really? That's like using a sledgehammer to crack a walnut. Way too heavy-handed for this requirement.
upvoted 0 times
Annabelle
4 days ago
A: Definitely, no need to go overboard with an approval process for this requirement.
upvoted 0 times
...
Edda
6 days ago
B: Yeah, that sounds like the most efficient way to handle it.
upvoted 0 times
...
Marylou
17 days ago
A: I think an Apex trigger on the Opportunity object would be the best option.
upvoted 0 times
...
Jacqueline
1 months ago
C: An approval process does seem like overkill for this specific requirement.
upvoted 0 times
...
Zita
1 months ago
B: Yeah, that sounds like the most efficient way to handle it.
upvoted 0 times
...
Brett
1 months ago
A: I think an Apex trigger on the Opportunity object would be the best option.
upvoted 0 times
...
...
Lorrie
2 months ago
A record trigger flow could also work, but it might be overkill for this specific use case. Seems like a bit more effort than necessary.
upvoted 0 times
...
Jennifer
2 months ago
I think the validation rule is a good choice too. It's a simple and efficient way to enforce the requirement without adding extra logic.
upvoted 0 times
Elbert
29 days ago
B: I agree, it's a straightforward way to enforce the restriction.
upvoted 0 times
...
Maryann
1 months ago
A: I think the validation rule is the best option for this requirement.
upvoted 0 times
...
Erick
1 months ago
B: I agree, it's a straightforward way to enforce the restriction.
upvoted 0 times
...
Marsha
2 months ago
A: I think the validation rule is the best option for this requirement.
upvoted 0 times
...
...
Gail
2 months ago
I'm not sure, but I think option A) An Apex trigger could also work. It allows for more customization.
upvoted 0 times
...
France
2 months ago
The trigger option seems like the most straightforward solution to me. It allows us to directly check the user's profile and the opportunity status change.
upvoted 0 times
Jame
22 days ago
An approval process might be too complex for this requirement, I would go with the Apex trigger option.
upvoted 0 times
...
Silvana
23 days ago
I think a record trigger flow could also work in this scenario, as it allows for more declarative automation.
upvoted 0 times
...
Huey
2 months ago
But wouldn't using a validation rule with an error condition formula be simpler and more efficient?
upvoted 0 times
...
Clay
2 months ago
I agree, using an Apex trigger would give us the flexibility to check both the user's profile and the opportunity status change.
upvoted 0 times
...
...
Ruth
3 months ago
I agree with Gerald. Using a validation rule would be the most efficient way to prevent unauthorized changes.
upvoted 0 times
...
Gerald
3 months ago
I think the best option is B) An error condition formula on a validation rule on Opportunity.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77