New Year Sale 2026! 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 Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 5 Question 23 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) exam
Question #: 23
Topic #: 5
[All Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) 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 Lavera at Aug 31, 2023, 01:32 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Donte
3 months ago
I think option D could work, but it sounds like a hassle.
upvoted 0 times
...
Blossom
4 months ago
Wait, reports can just roll back? That’s wild!
upvoted 0 times
...
Truman
4 months ago
Option B seems too extreme, let the execs have some control.
upvoted 0 times
...
Ceola
4 months ago
Totally agree, backups are crucial!
upvoted 0 times
...
Genevive
4 months ago
I heard option C is the best practice for this.
upvoted 0 times
...
Jacklyn
5 months ago
I think using a third-party data warehouse, as in option A, could help with data integrity, but I'm not sure if it directly addresses the rollback issue.
upvoted 0 times
...
Lorean
5 months ago
I feel like backing up reports before a release, like in option D, could work, but it sounds a bit manual. Is there a more automated way?
upvoted 0 times
...
Martin
5 months ago
I'm not entirely sure, but I think restricting access to reports might cause more issues than it solves. Option B seems a bit extreme.
upvoted 0 times
...
Whitney
5 months ago
I remember discussing how report metadata can sometimes get overwritten during releases. Maybe option C is the best way to handle that?
upvoted 0 times
...
Wade
5 months ago
I'm feeling pretty confident about this one. Option C is definitely the way to go - it'll ensure the report metadata is properly versioned and integrated into the development process.
upvoted 0 times
...
Nana
5 months ago
Okay, I think I've got a good handle on this. I'd recommend going with option C - that seems like the most robust and sustainable solution to me.
upvoted 0 times
...
Destiny
5 months ago
This seems like a tricky one. I'll need to think carefully about the different options and their potential impacts.
upvoted 0 times
...
Peggie
5 months ago
Hmm, I'm a bit confused by the question. I'll need to re-read it a few times to make sure I understand the problem and the possible solutions.
upvoted 0 times
...
Timothy
5 months ago
The Americans with Disabilities Act seems like a good option, since it deals with employee medical information. But I'll double-check the details.
upvoted 0 times
...
Luther
5 months ago
I'm drawing a blank on the TOGAF architecture types and their definitions. Maybe I should quickly review my notes before answering this one.
upvoted 0 times
...

Save Cancel