Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Development Lifecycle and Deployment Architect Topic 4 Question 38 Discussion

Actual exam question for Salesforce's Development Lifecycle and Deployment Architect exam
Question #: 38
Topic #: 4
[All Development Lifecycle and Deployment Architect Questions]

Universal Containers (UC) has a customized repository that represents lots of different

apps or projects. UC currently is trying to shift from the org development model to the package

development model to manage changes. In the org development model, each developer starts

their work within their own personal sandbox.

When it comes to choosing development environments, what should a Salesforce architect

recommend?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Ines
6 months ago
Scratch orgs? Sounds like a recipe for a lot of scratched heads if you ask me!
upvoted 0 times
Eden
5 months ago
Scratch orgs? Sounds like a recipe for a lot of scratched heads if you ask me!
upvoted 0 times
...
Devorah
5 months ago
B) Start using scratch orgs that tracks all of the changes automatically and proceed with a staggered approach since scratch orgs can coexist With other models.
upvoted 0 times
...
Lauran
6 months ago
A) Start using scratch orgs because a developer can spin up a scratch org to start a new project, start a new feature branch, or start automatedTesting.
upvoted 0 times
...
...
Mitsue
6 months ago
I agree with Lacey, scratch orgs allow for easier project management.
upvoted 0 times
...
Cyril
6 months ago
I heard scratch orgs can coexist with other models. Might as well give them a shot, right?
upvoted 0 times
...
Arlean
6 months ago
Sandboxes are like old friends - you just can't quit 'em, you know?
upvoted 0 times
...
Annabelle
6 months ago
Definitely go with scratch orgs! They're the future, and it's time to embrace the change.
upvoted 0 times
Nohemi
5 months ago
B) Start using scratch orgs that tracks all of the changes automatically and proceed with a staggered approach since scratch orgs can coexist With other models.
upvoted 0 times
...
William
5 months ago
A) Start using scratch orgs because a developer can spin up a scratch org to start a new project, start a new feature branch, or start automatedTesting.
upvoted 0 times
...
Murray
5 months ago
B) Start using scratch orgs that tracks all of the changes automatically and proceed with a staggered approach since scratch orgs can coexist With other models.
upvoted 0 times
...
Mariann
5 months ago
A) Start using scratch orgs because a developer can spin up a scratch org to start a new project, start a new feature branch, or start automatedTesting.
upvoted 0 times
...
Kristofer
6 months ago
Definitely go with scratch orgs! They're the future, and it's time to embrace the change.
upvoted 0 times
...
Deangelo
6 months ago
B) Start using scratch orgs that tracks all of the changes automatically and proceed with a staggered approach since scratch orgs can coexist With other models.
upvoted 0 times
...
Chauncey
6 months ago
B) Start using scratch orgs that tracks all of the changes automatically and proceed with a staggered approach since scratch orgs can coexist With other models.
upvoted 0 times
...
Casie
6 months ago
A) Start using scratch orgs because a developer can spin up a scratch org to start a new project, start a new feature branch, or start automatedTesting.
upvoted 0 times
...
Novella
6 months ago
A) Start using scratch orgs because a developer can spin up a scratch org to start a new project, start a new feature branch, or start automatedTesting.
upvoted 0 times
...
...
Lacey
6 months ago
I think we should start using scratch orgs for better development.
upvoted 0 times
...

Save Cancel