Salesforce Certified B2B Solution Architect (Arch-301) Exam - Topic 5 Question 55 Discussion

Actual exam question for Salesforce's Salesforce Certified B2B Solution Architect (Arch-301) exam

Question #: 55
Topic #: 5

[All Salesforce Certified B2B Solution Architect (Arch-301) Questions]

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

AUse multiple development sandboxes and merge the workstream builds using change sets.

BUse a version control system and CLI-based deployment tools to merge the workstream builds.

CUse scratch orgs and continuous deployment tools to merge the workstream builds.

DUse package-based deployments and scratch orgs to merge the workstream builds.

Show Suggested Answer

Suggested Answer: B, C

by Elke at Apr 06, 2025, 10:05 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified B2B Solution Architect (Arch-301) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Magdalene

2 months ago

Wait, are we sure multiple sandboxes won't complicate things more?

upvoted 0 times

...

Pearlene

2 months ago

Not sure about D, package-based deployments can get tricky.

upvoted 0 times

...

Solange

2 months ago

I think C is the way to go, scratch orgs are super flexible!

upvoted 0 times

...

Shaniqua

3 months ago

Totally agree with A, change sets are easy to use!

upvoted 0 times

...

Sommer

3 months ago

A and B seem like solid options for managing the builds.

upvoted 0 times

...

Tina

3 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.

upvoted 0 times

...

Lili

3 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.

upvoted 0 times

...

Ming

4 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.

upvoted 0 times

...

Gracia

4 months 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.

upvoted 0 times

...

Beckie

4 months 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.

upvoted 0 times

...

Billi

4 months ago

Scratch orgs and continuous deployment tools could also be a solid option. That would allow for more automated merging and testing.

upvoted 0 times

...

Fernanda

4 months 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.

upvoted 0 times

...

Dianne

5 months ago

Okay, let me think this through. We need to consider options that support multiple implementation workstreams and a more rigorous change management process.

upvoted 0 times

...

Ira

5 months ago

This question seems straightforward, but I want to make sure I understand the requirements fully before answering.

upvoted 0 times

...

Leanora

10 months ago

I think using package-based deployments and scratch orgs could also be a good option to support both implementation workstreams.

upvoted 0 times

...

Shawnda

10 months 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!

upvoted 0 times

Remedios

8 months 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!

upvoted 0 times

...

Glory

9 months ago

B) Use a version control system and CLI-based deployment tools to merge the workstream builds.

upvoted 0 times

...

Gabriele

10 months ago

A) Use multiple development sandboxes and merge the workstream builds using change sets.

upvoted 0 times

...

Lavera

10 months 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?

upvoted 0 times

...

Karan

10 months 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!

upvoted 0 times

...

Shonda

10 months ago

I agree with Rashad. It would ensure a more organized and controlled process for the implementation workstreams.

upvoted 0 times

...

Ulysses

11 months 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.

upvoted 0 times

Kasandra

9 months 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.

upvoted 0 times

...