BlackFriday 2024! 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 5 Question 39 Discussion

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

Universal Containers are concerned that after each release, reports and dashboards

seem to roll back to previous versions. Executives spend many hours crafting these dashboards to perfectly meet their needs, and are now questioning the Salesforce platform's ability to save things, even data records.

What can the Salesforce architect advise to stop the rollbacks from happening?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Della at Jun 21, 2024, 05:17 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
Emerson
4 months ago
I don't know, option B sounds pretty tempting. Taking away the exec's ability to change reports might stop the rollbacks, but it could also cause some serious headaches.
upvoted 0 times
Shelia
3 months ago
Yeah, I think option C is the way to go. It's better to be safe than sorry when it comes to important reports and dashboards.
upvoted 0 times
...
Chana
3 months ago
I agree with Gerald and Chana. Option C seems like a proactive approach to avoid the rollbacks.
upvoted 0 times
...
Gerald
3 months ago
Gerald, that's a good point. It could help ensure that the reports are saved before any potential issues arise.
upvoted 0 times
...
Rosamond
3 months ago
I think option C could work. Exporting report metadata daily sounds like a good way to prevent rollbacks.
upvoted 0 times
...
Angelyn
3 months ago
B) Remove the executive's ability to change reports, and only allow developers to do that.
upvoted 0 times
...
Hector
3 months ago
A) Use a third-party data warehouse.
upvoted 0 times
...
...
Josue
4 months ago
I think using a third-party data warehouse could also be a good option to prevent rollbacks.
upvoted 0 times
...
Iola
5 months ago
I prefer option D, backing up reports before the release gives a safety net.
upvoted 0 times
...
Dominic
5 months ago
Haha, the executives must be really frustrated if they're 'questioning the Salesforce platform's ability to save things'. Option C is the best way to address this issue.
upvoted 0 times
Theron
4 months ago
Option C sounds like a good solution to prevent the rollbacks from happening.
upvoted 0 times
...
Adaline
4 months ago
Option C) Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.
upvoted 0 times
...
...
Nada
5 months ago
I agree with Milly, exporting report metadata daily seems like a proactive approach.
upvoted 0 times
...
Victor
5 months ago
I agree with John, option C is the way to go. Backing up reports and reimporting them after the release seems like a lot of extra work.
upvoted 0 times
...
Milly
5 months ago
I think option C sounds like a good solution.
upvoted 0 times
...
Josefa
5 months ago
Option C seems like the most logical solution. Ensuring the report metadata is exported and merged into the developer branches before the next release sounds like a solid plan to avoid the rollbacks.
upvoted 0 times
Eun
4 months ago
That makes sense, exporting and merging the report metadata before the release should prevent the rollbacks.
upvoted 0 times
...
Tijuana
4 months ago
Agreed, it seems like the most logical solution.
upvoted 0 times
...
Izetta
5 months ago
I think option C is the way to go.
upvoted 0 times
...
...

Save Cancel