MENU
Universal Containers (UC) is in the process of identifying if Revenue Cloud will work for its business processes. UC has already implemented Sales Cloud, which includes complex steps and checklists that are orchestrated based on changes made to an Opportunity. Based on the current Sales Cloud implementation, UC has concerns about how Revenue Cloud will interact with its current customizations on the Opportunity object and if it will be difficult to customize the solution in the future.
Which design approach should a Solution Architect recommend tomitigate concerns about custom processes on any single object?
Suggested Answer: C
Get Premium ARC-801 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
This will ensure that all orders are stored in a single, unified database, and will make it easier to track and manage orders across different channels. Additionally, Salesforce Order Objects have built-in features that make it easy to integrate with ERP systems, B2B Commerce, and Marketing Cloud, allowing UC to create the desired fluidity between its application landscape.
43 comments · newest first
ED
Edna
11 months ago
I’ve heard good things about C, but not sure it’s the best choice here.
GR
Gracia
11 months ago
D could work too, separating before and after saves sounds smart.
WH
Whitney
12 months ago
Surprised that they’re still using Process Builder, isn’t it outdated?
IR
Iraida
12 months ago
I disagree, B seems more straightforward for managing updates.
BU
Buddy
1 year ago
I think option A is the best for keeping things flexible.
AL
Alease
1 year ago
I recall we practiced a similar question where invoking autolaunched flows from Process Builder was mentioned. It seems like a safe option, but is it really the most efficient?
TO
Toshia
1 year ago
I feel like separating flows for 'Before Save' and 'After Save' could be a good approach, but it might complicate the overall process.
JA
Jamal
1 year ago
I think using a single flow for all operations could simplify things, but what if it becomes too complex to manage later on?
BI
Billi
1 year ago
I remember we discussed how event-driven design can help with scalability, but I'm not sure if Heroku is the best fit for UC's needs.
ST
Steffanie
1 year ago
I feel pretty confident about this question. Based on the information provided, I think option A is the best way to address the concerns about custom processes on the Opportunity object. The event-driven design should help decouple the automations from the save cycle.
MA
Markus
1 year ago
This is a tough one. There are a few different approaches, and I'm not entirely sure which one would be the most effective. I'll need to weigh the pros and cons of each option carefully.
HE
Herman
1 year ago
Okay, I've reviewed the question a few times and I think I've got a solid strategy. I'm leaning towards option B, but I'll need to double-check the details to make sure it's the best fit.
ED
Edna
1 year ago
Hmm, the question is asking about the best design approach to mitigate concerns about custom processes on a single object. I think I have a good handle on the options, but I'll need to carefully consider the tradeoffs.
BL
Blythe
1 year ago
This question seems straightforward, but I want to make sure I understand the key requirements before answering.
XO
Xochitl
1 year ago
I'm feeling confident about this one. The data custodian implements the classification scheme after the initial assignment by the data owner.
CA
Carmelina
1 year ago
Hmm, I'm not sure about this. Capturing cost of work order bookings seems tricky. I'll need to think this through carefully.
AL
Alethea
1 year ago
Hmm, I'm not totally sure about this one. I know the waterfall method has a lot of steps, so I'll have to think it through carefully.
KA
Kathrine
1 year ago
Option C? Really? Invoking autolaunched flows from Process Builder? That's like trying to fit a square peg in a round hole. Hard pass!
KE
Keneth
1 year ago
Option A with Heroku sounds like a cool idea, but it might be overkill for this use case. I'd stick to the native Salesforce options to keep things simple.
AS
Asuncion
1 year ago
True, but it might be more complex to set up and maintain compared to the other options.
DE
Delsie
1 year ago
But what about separating automations with an event-driven design? That could be useful for complex processes.
SH
Shayne
1 year ago
I think using a single flow triggered by record updates could help organize operations effectively.
MO
Mozell
1 year ago
I agree, sticking to native Salesforce options would be more straightforward.
NO
Nohemi
2 years ago
I'm leaning towards Option B. Consolidating all the automations into a single flow triggered by record updates sounds like a neat way to keep everything organized and manageable.
JE
Jennie
1 year ago
Using an event-driven design with a third-party tool like Heroku could also be a good way to mitigate concerns about custom processes.
LI
Lindsey
1 year ago
I think Option D could also work well by separating operations into different flows for 'Before Save' and 'After Save'.
FE
Felicitas
1 year ago
I agree, Option B seems like a good approach to keep things organized.
LE
Leanna
2 years ago
I agree with Ashton. Separating the automations into 'Before Save' and 'After Save' flows will make the solution more modular and easier to maintain in the long run.
JO
Jolanda
1 year ago
D) Migrate automations from Process Builder to flows triggered by record updates, organizing operations in separate flows for the 'Before Save' and 'After Save' contexts.
PE
Pearly
1 year ago
I agree with Ashton. Separating the automations into 'Before Save' and 'After Save' flows will make the solution more modular and easier to maintain in the long run.
AR
Argelia
1 year ago
D) Migrate automations from Process Builder to flows triggered by record updates, organizing operations in separate flows for the 'Before Save' and 'After Save' contexts.
LA
Layla
1 year ago
B) Migrate automations from Process Builder to a single flow that is triggered by record updates, using only the 'After Save' context so that all operations can be organized in a single flow.
GE
Geraldo
1 year ago
A) Use an event-driven design to separate automations that could run asynchronously from the save cycle with a third-party tool like Heroku.
JE
Jeannetta
1 year ago
B) Migrate automations from Process Builder to a single flow that is triggered by record updates, using only the 'After Save' context so that all operations can be organized in a single flow.
HE
Hector
1 year ago
A) Use an event-driven design to separate automations that could run asynchronously from the save cycle with a third-party tool like Heroku.
AS
Ashton
2 years ago
Option D seems like the best approach to separate the automation logic from the Opportunity object. This way, we can have better control and organization over the different operations that need to be executed before and after saving the record.
SO
Soledad
2 years ago
I'm not sure, I think option A might also work well to separate automations and avoid conflicts.
LA
Laurel
2 years ago
I agree with you, Rosenda. Option D seems to be the best choice to organize operations effectively.
RO
Rosenda
2 years ago
I think option D sounds like a good approach.
PA
Paris
2 years ago
Using an event-driven design with a third-party tool like Heroku will help us separate automations and avoid potential conflicts with our custom processes.
TE
Teri
2 years ago
Why do you think option A is better?
PA
Paris
2 years ago
I disagree, I believe option A is the best approach.
TE
Teri
2 years ago
I think we should go with option D.