Salesforce Exam Development Lifecycle and Deployment Architect Topic 7 Question 31 Discussion

Actual exam question for Salesforce's Development Lifecycle and Deployment Architect exam

Question #: 31
Topic #: 7

[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?

AUse a third-party data warehouse.

BRemove the executive's ability to change reports, and only allow developers to do that.

CEnsure report metadata is exported daily and that it is merged into the developer branches
before the next release.

DBack up all the reports just before the release, then reimport them after the release,

Show Suggested Answer

Suggested Answer: C

by Nicolette at Mar 09, 2024, 05:14 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

Graciela

6 months ago

I disagree, using a third-party data warehouse could be a better solution to prevent rollbacks.

upvoted 0 times

...

Milly

7 months ago

I don't know, guys. Backing up and reimporting the reports sounds like a lot of manual work. Maybe we could auReikoate that process somehow? Ooh, or what if we set up a trigger to save the report metadata on every change? Just throwing ideas out there.

upvoted 0 times

Jordan

5 months ago

C) Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.

upvoted 0 times

...

Zena

6 months ago

A) Use a third-party data warehouse.

upvoted 0 times

...

Cecilia

7 months ago

Wait, are we sure the reports aren't just being sabotaged by the interns? Just kidding, but seriously, the report backup and reimport option sounds like the most straightforward solution here.

upvoted 0 times

Gracia

6 months ago

C) Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.

upvoted 0 times

...

Truman

6 months ago

A) Use a third-party data warehouse.

upvoted 0 times

...

Britt

7 months ago

A third-party data warehouse? That's overkill for this problem. I'm with Gilma on this one - the report metadata export and merge is the way to go. Keeps the executives happy and the platform running smoothly.

upvoted 0 times

Meaghan

6 months ago

I'm with Gilma on this one - the report metadata export and merge is the way to go. Keeps the executives happy and the platform running smoothly.

upvoted 0 times

...

Herschel

6 months ago

A third-party data warehouse? That's overkill for this problem.

upvoted 0 times

...

Reiko

7 months ago

Removing the executives' ability to change reports? Yikes, that's a surefire way to get on their bad side. I'd go with the option to back up the reports before the release and then reimport them. Seems like a safer bet.

upvoted 0 times

...

Gilma

7 months ago

Hmm, this is a tricky one. I think the solution is to ensure the report metadata is properly exported and merged into the developer branches before the next release. Anything less could lead to some serious headaches down the line.

upvoted 0 times