New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Platform Developer II (Plat-Dev-301) Exam - Topic 4 Question 58 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Developer II (Plat-Dev-301) exam
Question #: 58
Topic #: 4
[All Salesforce Certified Platform Developer II (Plat-Dev-301) Questions]

A developer created an Opportunity trigger that updates the account rating when an associated opportunity is considered high value. Current criteria for an opportunity to be considered high value is an amount greater than or equal to SI,000,000. However, this criteria value can change over time.

There is a new requirement to also display high value opportunities In a Lightning web component.

Which two actions should the developer take to prevent the business logic that obtains the high value opportunities from being repeated in more than one place?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, D

Contribute your Thoughts:

0/2000 characters
Aleisha
4 months ago
Wait, can we really just change the amount in custom metadata? That’s cool!
upvoted 0 times
...
Lili
4 months ago
B is a no-go, triggers should handle logic, not components!
upvoted 0 times
...
Lilli
4 months ago
D sounds good too, but I’m not sure if it’s necessary.
upvoted 0 times
...
Deja
4 months ago
Totally agree, A makes it easier to manage changes!
upvoted 0 times
...
Kathrine
4 months ago
A is a solid choice for keeping the amount flexible.
upvoted 0 times
...
Willetta
5 months ago
I feel like leaving the logic in the trigger might lead to duplication issues later on, but I’m not completely confident about that.
upvoted 0 times
...
Johnson
5 months ago
Creating a helper class sounds familiar. It could help keep the logic centralized and reusable, right?
upvoted 0 times
...
Tennie
5 months ago
I'm not entirely sure, but I think calling the trigger from the Lightning web component might not be the best approach.
upvoted 0 times
...
Moira
5 months ago
I remember we discussed using custom metadata for storing values like the high value amount. It seems like a good option here.
upvoted 0 times
...
Diego
5 months ago
Hmm, this looks like a straightforward question about the Knowledge table. I'll need to think carefully about the options and make sure I understand the relationship between the Knowledge table and other tables in the system.
upvoted 0 times
...
Tawny
5 months ago
Whoa, this is a lot of information to process. I'm a bit confused about how sequences work and how they interact with table columns. I'll need to review my notes on that.
upvoted 0 times
...
Caitlin
5 months ago
Hmm, I'm a bit unsure about this one. I think it might be schedule variance, but I'm not totally sure. I'll have to think it through carefully.
upvoted 0 times
...

Save Cancel