MENU
AC Computers has decided to extend its existing Sales Cloud solution by implementing Service Cloud and Marketing Cloud Account Engagement. AC Computers has defined two different work streams for Service Cloud and Marketing Cloud Account Engagement and wants each workstream to work iteratively in separate sandboxes and migrate to a single sandbox for UAT and integration testing. With the multiple workstreams, AC Computers needs a more rigorous change management process and an audit process.
Which two options should AC Computers consider to support both implementation workstreams?
Choose 2 answers
Suggested Answer: B, C
Get Premium Salesforce Certified B2B Solution Architect (Arch-301) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
MA
Magdalene
10 months ago
Wait, are we sure multiple sandboxes won't complicate things more?
PE
Pearlene
11 months ago
Not sure about D, package-based deployments can get tricky.
SO
Solange
11 months ago
I think C is the way to go, scratch orgs are super flexible!
SH
Shaniqua
11 months ago
Totally agree with A, change sets are easy to use!
SO
Sommer
11 months ago
A and B seem like solid options for managing the builds.
TI
Tina
11 months ago
I vaguely recall something about package-based deployments being beneficial for larger projects. Option D could be a solid choice, but I’m not completely confident.
LI
Lili
12 months ago
I practiced a similar question about deployment strategies, and I think scratch orgs are really useful. Option C might be the way to go for continuous integration.
MI
Ming
12 months ago
I’m not entirely sure, but I think using multiple development sandboxes might complicate things. Option A sounds familiar, but I feel like it could lead to issues with merging.
GR
Gracia
1 year ago
I remember we discussed the importance of using version control systems for managing multiple workstreams. It seems like option B could be a good fit.
BE
Beckie
1 year ago
I'm a bit unsure about the package-based deployments and scratch orgs approach. I'll need to research that one a bit more to see if it fits the requirements.
BI
Billi
1 year ago
Scratch orgs and continuous deployment tools could also be a solid option. That would allow for more automated merging and testing.
FE
Fernanda
1 year ago
I'm leaning towards using version control and CLI-based deployment tools. That seems like a good way to manage the merging of the workstream builds.
DI
Dianne
1 year ago
Okay, let me think this through. We need to consider options that support multiple implementation workstreams and a more rigorous change management process.
IR
Ira
1 year ago
This question seems straightforward, but I want to make sure I understand the requirements fully before answering.
LE
Leanora
2 years ago
I think using package-based deployments and scratch orgs could also be a good option to support both implementation workstreams.
SH
Shawnda
2 years ago
B) is the way to go, no doubt. Version control and CLI tools are the adult version of using a rock and a chisel to carve your code. Much more efficient!
RE
Remedios
1 year ago
B) is the way to go, no doubt. Version control and CLI tools are the adult version of using a rock and a chisel to carve your code. Much more efficient!
GL
Glory
1 year ago
B) Use a version control system and CLI-based deployment tools to merge the workstream builds.
GA
Gabriele
2 years ago
A) Use multiple development sandboxes and merge the workstream builds using change sets.
LA
Lavera
2 years ago
D) for the win! Package-based deployments and scratch orgs are the way to go. Keeps everything nice and tidy, you know? Plus, who doesn't love a good scratch org, am I right?
KA
Karan
2 years ago
Scratch orgs? More like 'scratching my head' orgs, am I right? But seriously, C) is the way to go. Gotta keep up with the times, people!
SH
Shonda
2 years ago
I agree with Rashad. It would ensure a more organized and controlled process for the implementation workstreams.
UL
Ulysses
2 years ago
B) is the way to go! Version control and CLI tools will make it easy to manage multiple workstreams and merge the builds. Sandboxes and scratch orgs can get messy with all the moving parts.
KA
Kasandra
1 year ago
B) is the way to go! Version control and CLI tools will make it easy to manage multiple workstreams and merge the builds. Sandboxes and scratch orgs can get messy with all the moving parts.
XO
Xochitl
1 year ago
A) Use multiple development sandboxes and merge the workstream builds using change sets.
RO
Roselle
1 year ago
B) Use a version control system and CLI-based deployment tools to merge the workstream builds.
KR
Kristeen
1 year ago
D) Use package-based deployments and scratch orgs to merge the workstream builds.
AV
Avery
1 year ago
B) is definitely the best option for managing multiple workstreams efficiently.
NI
Nikita
1 year ago
A) Use multiple development sandboxes and merge the workstream builds using change sets.
AN
Antonio
1 year ago
B) Use a version control system and CLI-based deployment tools to merge the workstream builds.
RA
Rashad
2 years ago
I think AC Computers should consider using multiple development sandboxes and merge the workstream builds using change sets.