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 4 Question 41 Discussion

Actual exam question for Salesforce's Salesforce Certified Development Lifecycle and Deployment Architect exam
Question #: 41
Topic #: 4
[All Salesforce Certified 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 Ressie at Jul 08, 2024, 04:51 AM

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
Lynna
18 days ago
Ooh, a third-party data warehouse, huh? Sounds like someone's been watching too many Silicon Valley episodes. Let's stick to the Salesforce platform, shall we?
upvoted 0 times
...
Gene
22 days ago
Gotta love those execs who want everything 'just so.' Option B is a bit heavy-handed, don't you think? 'Only developers can touch the reports' - yeah, that'll go over well.
upvoted 0 times
...
Catalina
27 days ago
This is a classic case of 'if it ain't broke, don't fix it.' Why not just back up the reports and reimport them? Simple and effective, like a good engineer.
upvoted 0 times
Delpha
20 days ago
C) Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.
upvoted 0 times
...
...
Rossana
1 months ago
I agree with Dorothea. Maintaining version control on the report metadata is the key to preventing those frustrating rollbacks.
upvoted 0 times
Billy
13 days ago
B) Remove the executive's ability to change reports, and only allow developers to do that.
upvoted 0 times
...
Clement
26 days ago
A) Use a third-party data warehouse.
upvoted 0 times
...
...
Lynelle
1 months ago
I think using a third-party data warehouse could also be a good idea to prevent rollbacks.
upvoted 0 times
...
Kattie
1 months ago
I prefer option D, backing up reports before the release gives us a safety net.
upvoted 0 times
...
Dorothea
2 months ago
Option C is the way to go. Exporting the report metadata and merging it into the developer branches is the best way to ensure consistency across releases.
upvoted 0 times
Leontine
11 days ago
Billy: It will definitely save a lot of time and effort for the executives crafting those dashboards.
upvoted 0 times
...
Markus
12 days ago
User 3: That sounds like a good plan, making sure everything is merged before the next release.
upvoted 0 times
...
Billy
22 days ago
User 2: I agree, it's important to export the report metadata daily to avoid losing any changes.
upvoted 0 times
...
Margurite
28 days ago
User 1: Option C is definitely the best solution to prevent rollbacks.
upvoted 0 times
...
...
Nikita
2 months ago
I agree with Francis, exporting report metadata daily seems like a proactive approach.
upvoted 0 times
...
Francis
2 months ago
I think option C sounds like a good solution.
upvoted 0 times
...

Save Cancel