Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Development Lifecycle and Deployment Architect Topic 8 Question 20 Discussion

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

Universal Containers CUC) is looking for advice on how often it should refresh its sandboxes. UC currently uses a development Mfecycle that starts with developer environments and moves to integration testing, QA testing, UAT, and then production. They have many scrum teams working concurrently and the teams do not agree on when refreshes should occur.

What two recommendations should the architect suggest?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A

by Shawnda at Jul 09, 2023, 11:38 PM

Limited Time Offer

25%

Off

Get Premium Development Lifecycle and Deployment Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Jenise
1 months ago
Wow, these options are a real mixed bag. Sounds like the UC team needs to get on the same page about their sandbox refresh strategy.
upvoted 0 times
Wava
9 days ago
Yeah, it seems like there's a lack of consistency in their approach. They definitely need to align on when and how often to refresh their sandboxes.
upvoted 0 times
...
Jacquelyne
24 days ago
D) Development environments should generally be refreshed after each working feature has been successfully migrated.
upvoted 0 times
...
Lucia
1 months ago
A) Sandboxes should be refreshed on the day when the refresh is allowed for that type of sandbox.
upvoted 0 times
...
...
Samira
2 months ago
I'm just glad they're not asking us to refresh the production environment daily. Talk about a recipe for disaster!
upvoted 0 times
Gerry
2 days ago
I'm just glad they're not asking us to refresh the production environment daily. Talk about a recipe for disaster!
upvoted 0 times
...
Blair
12 days ago
D) Development environments should generally be refreshed after each working feature has been successfully migrated.
upvoted 0 times
...
Kayleigh
1 months ago
A) Sandboxes should be refreshed on the day when the refresh is allowed for that type of sandbox.
upvoted 0 times
...
...
Bobbie
2 months ago
C is a terrible idea. Maintaining APIs is crucial, so refreshing integration sandboxes rarely would be a big mistake.
upvoted 0 times
...
Carolann
2 months ago
B is just plain wrong. Production shouldn't be the only pristine environment - that's a disaster waiting to happen!
upvoted 0 times
...
Earleen
2 months ago
But shouldn't we also consider refreshing development environments after each feature migration?
upvoted 0 times
...
Dallas
2 months ago
I agree with that. It helps keep everything up to date.
upvoted 0 times
...
Lawana
2 months ago
I think we should refresh sandboxes on the day when it's allowed.
upvoted 0 times
...
Alida
2 months ago
But won't frequent refreshes cause disruptions in our work?
upvoted 0 times
...
Earleen
2 months ago
I agree with Micaela, it helps in maintaining a clean development environment.
upvoted 0 times
...
Micaela
2 months ago
I think we should refresh sandboxes after each working feature is migrated.
upvoted 0 times
...
Sheron
2 months ago
A and D seem like the way to go. Refreshing sandboxes on a set schedule and after feature migrations makes a lot of sense to keep everything in sync.
upvoted 0 times
Evangelina
15 days ago
Yeah, having a clear distinction for the production environment is crucial for data integrity.
upvoted 0 times
...
Sherell
16 days ago
I think Production being the only pristine environment makes sense too.
upvoted 0 times
...
Luke
24 days ago
I agree, it's important to maintain consistency across environments.
upvoted 0 times
...
Jolene
2 months ago
A and D seem like the way to go. Refreshing sandboxes on a set schedule and after feature migrations makes a lot of sense to keep everything in sync.
upvoted 0 times
...
...

Save Cancel