Salesforce Exam Development Lifecycle and Deployment Architect Topic 4 Question 41 Discussion

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

Question #: 41
Topic #: 4

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

3 months 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

3 months 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

Laine

2 months ago

Gotta find a balance between control and flexibility.

upvoted 0 times

...

Marge

2 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

...

Katy

2 months ago

A) Use a third-party data warehouse.

upvoted 0 times

...

Catalina

4 months 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

Lawrence

2 months ago

A) Use a third-party data warehouse.

upvoted 0 times

...

Princess

3 months ago

D) Back up all the reports just before the release, then reimport them after the release.

upvoted 0 times

...

Delpha

3 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

...

Rossana

4 months ago

I agree with Dorothea. Maintaining version control on the report metadata is the key to preventing those frustrating rollbacks.

upvoted 0 times

Annice

2 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

...

Billy

3 months ago

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

upvoted 0 times

...

Clement

3 months ago

A) Use a third-party data warehouse.

upvoted 0 times

...

Lynelle

4 months ago

I think using a third-party data warehouse could also be a good idea to prevent rollbacks.

upvoted 0 times

...

Kattie

4 months ago

I prefer option D, backing up reports before the release gives us a safety net.

upvoted 0 times

...

Dorothea

4 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