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 3 Question 51 Discussion

Actual exam question for Salesforce's Development Lifecycle and Deployment Architect exam
Question #: 51
Topic #: 3
[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:

Dante
16 days ago
Scratch orgs? Sounds like the Salesforce version of virtual machines. I bet the IT guys are gonna love all the extra setup and maintenance. But hey, if it works, I'm in!
upvoted 0 times
...
Lorrie
18 days ago
Haha, I love the idea of a 'personal sandbox' for each developer. It's like having our own little coding playgrounds. But seriously, I think scratch orgs are the way to go. Automatic change tracking? Sign me up!
upvoted 0 times
Brice
3 days 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
...
Chun
5 days 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
...
Brynn
8 days 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
...
...
Regenia
24 days ago
Scratch orgs? Nah, man. I'm sticking with my trusty dev sandboxes. They may not be as fancy, but at least I know they're part of the deployment path. No surprises here!
upvoted 0 times
...
Maurine
28 days ago
I'm all for the package development model, but I'm not sure scratch orgs are the answer. What about those staggered sandbox approaches? Sounds like a good way to ease into the transition.
upvoted 0 times
Mollie
6 days 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
...
Christiane
7 days 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
...
...
Alease
2 months ago
I disagree, I believe B) Start using scratch orgs that tracks all changes automatically is the way to go for better tracking and collaboration.
upvoted 0 times
...
Brianne
2 months ago
I think A) Start using scratch orgs because it allows for a more agile development process.
upvoted 0 times
...
Avery
2 months ago
Scratch orgs all the way! They're like the new shiny toy in the Salesforce development sandbox. I can't wait to spin one up and start coding like a madman.
upvoted 0 times
Zachary
28 days 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
...
Devorah
1 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
...
Carey
1 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
...
...

Save Cancel