Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce DEX-450 Exam - Topic 11 Question 99 Discussion

Posted by Shaun on Sep 14, 2024 at 11:59 AM

Universal Containers wants Opportunities to no longer be editable when it reaches the Closed/Won stage.

Which two strategies can a developer use to accomplish this?

Choose 2 answers

Suggested Answer: B

Get Premium DEX-450 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
38 comments · newest first
CH
Charlette 11 months ago
I agree with A, but C is a bit overkill for this.
DA
Dahlia 11 months ago
Wait, can you really lock fields with just a validation rule?
MI
Miriam 12 months ago
Definitely A, but D seems unnecessary.
CE
Celestina 12 months ago
I think B could work too, but not really sure.
AL
Allene 1 year ago
A and C are the best options!
GI
Gilma 1 year ago
I’m leaning towards the validation rule and the Apex trigger, but I wish I had reviewed more about Approval Processes before the exam.
KA
Karima 1 year ago
Auto-response rules don't seem relevant here, right? I feel like they’re more for managing emails than record edits.
AR
Arlyne 1 year ago
I remember practicing a question about making records read-only, and I think a before-save Apex trigger might be a good choice too.
DU
Dulce 1 year ago
I think using a validation rule could work to prevent edits once the Opportunity is Closed/Won, but I'm not entirely sure if it's the best option.
FR
France 1 year ago
This is a good question. I think the key is to find a way to lock down the Opportunity record once it reaches the Closed/Won stage. A validation rule or an Apex trigger could both work, but I'll need to consider the pros and cons of each approach.
TA
Tawna 1 year ago
I'm a bit confused on this one. I know we can use validation rules and triggers, but I'm not sure which one would be the better option here. I'll have to think this through carefully.
IV
Ivan 1 year ago
Okay, let's see. A validation rule could work, but I'm not sure if that would be the best approach. Maybe an auto-response rule or an approval process would be better.
MA
Margurite 1 year ago
Hmm, this seems straightforward. I think I'll go with a validation rule and an Apex trigger to cover all my bases.
LA
Lazaro 1 year ago
Okay, let me break this down. The question is saying top-down is often easier because drivers are easier to create than stubs. I'll need to consider the differences between the two approaches.
HY
Hyun 1 year ago
Ooh, this one's a doozy. I think I'm gonna go with B) and D) - an auto-response rule and an approval process. Gotta love these certification exams, they really keep you on your toes!
DO
Donette 1 year ago
↳ replying to Hyun
I'm not sure about A) and C). I think D) might be a good choice for locking down Opportunities at the Closed/Won stage.
JA
Jaime 1 year ago
↳ replying to Hyun
I agree with you, A) and C) are the way to go. They provide more control over the editing restrictions.
MA
Martina 1 year ago
↳ replying to Hyun
I think A) and C) would be better options. Validation rule and before-save Apex trigger seem more appropriate.
ER
Erick 2 years ago
Haha, I'm just picturing the developer who has to implement this. Talk about job security! *chuckles* Anyway, I'd go with C) and D) - a trigger and an approval process should do the trick.
DA
Dana 1 year ago
↳ replying to Erick
D) Use an automatically launched Approval Process.
WE
Wei 1 year ago
↳ replying to Erick
C) Use a before-save Apex trigger.
LO
Louis 1 year ago
↳ replying to Erick
A) Use a validation rule.
FE
Felix 2 years ago
Hmm, this is a tricky one. I'm leaning towards A) and C) - a validation rule and a trigger might be the way to go. Gotta love these certification questions, they really make you think!
JE
Jenise 1 year ago
↳ replying to Felix
Definitely. A validation rule and a trigger are common strategies for enforcing data integrity in Salesforce.
JO
Joaquin 1 year ago
↳ replying to Felix
I'm not sure about B) and D), but A) and C) definitely make sense for this scenario.
AN
Anthony 1 year ago
↳ replying to Felix
Yeah, I agree. Those two options seem like the most logical choices for making Opportunities uneditable in the Closed/Won stage.
SY
Sylvie 1 year ago
↳ replying to Felix
I think A) and C) are the best options too. A validation rule and a trigger should do the trick.
BR
Brock 2 years ago
I'm feeling pretty confident about this one. I think the right answers are B) and D) - an auto-response rule and an approval process should do the trick.
TE
Tess 1 year ago
↳ replying to Brock
User 2: I agree, an auto-response rule and an approval process should work.
LA
Lai 1 year ago
↳ replying to Brock
User 1: I think B) and D) are the right choices.
KA
Kate 2 years ago
I think using a before-save Apex trigger could also be a good strategy to accomplish this.
CU
Curtis 2 years ago
I agree with Alisha, a validation rule can help prevent editing at Closed/Won stage.
AL
Alisha 2 years ago
I think using a validation rule would be a good strategy.
CH
Cheryl 2 years ago
Definitely going with C) and D) on this one. A trigger and an approval process seem like the best way to lock down the Opportunity once it's closed won.
PA
Pansy 1 year ago
↳ replying to Cheryl
I agree, those two options provide the most control over the Opportunity's status and prevent any unauthorized changes.
PR
Princess 2 years ago
↳ replying to Cheryl
I think using a trigger and an approval process is the most secure way to handle this requirement.
MA
Margarett 2 years ago
↳ replying to Cheryl
A validation rule could also be helpful in ensuring data integrity before the Opportunity reaches Closed/Won stage.
LA
Lashanda 2 years ago
↳ replying to Cheryl
I agree, using a before-save Apex trigger and an automatically launched Approval Process would be the best way to prevent editing of Opportunities in Closed/Won stage.
0/2000 characters

Save Cancel