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

Salesforce Exam B2B Solution Architect Topic 3 Question 56 Discussion

Actual exam question for Salesforce's B2B Solution Architect exam
Question #: 56
Topic #: 3
[All B2B Solution Architect Questions]

Universal Containers (UC) recently completed its migration to Lightning Experience, with sales users automatically moving to Lightning. This initiative was a massive undertaking by UC, as it had a tremendous amount of legacy functionality migrated over to Lightning from Classic. The CIO would like to make sure that UC is able to track adoption of the migrated functionality over from Classic to Lightning and what specifically was migrated.

Which two proposals should a Solution Architect recommend?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B, C

The two proposals a Solution Architect should recommend to track adoption of migrated functionality from Classic to Lightning are:

B) Track Adoption Rates within the Lightning Usage, and monitor a change in metrics within existing reports and dashboards. C. Provide the CIO a list of the User Stories around the new functionality and the Gap Analysis donebetween Classic and Lightning.

Tracking adoption rates and success metrics is one of the best practices for driving Lightning Experience adoption, as it allows UC to measure how well users are using the migrated functionality and identify areas of improvement or feedback.According to2, monitoring a change in metrics within existing reports and dashboards can also help UC evaluatethe impact of Lightning Experience on their business performance and user satisfaction.

Providing a list of user stories around the new functionality can help UC communicate the benefits and value of Lightning Experience to their users and stakeholders, aswell as align their expectations and goals with the migration project.According to3, providing a gap analysis done between Classic and Lightning can also helpUC understand what features or customizations are available or not available in Lightning Experience, as well as plan for any necessary changes or enhancements.

https://trailhead.salesforce.com/content/learn/modules/lex_migration_rollout/lex_migration_rollout_enabling


Contribute your Thoughts:

William
16 days ago
I don't think we need to roll back all changes. Once we migrate, we should stick with Lightning.
upvoted 0 times
...
Chaya
25 days ago
We should also provide the CIO a list of User Stories and Gap Analysis.
upvoted 0 times
...
Micah
27 days ago
I agree with that. It's important to monitor the change in metrics.
upvoted 0 times
...
Detra
27 days ago
I agree, B and C are the way to go. But I'm a little concerned about option D - the data created in Classic and Lightning should be the same? That doesn't sound right to me.
upvoted 0 times
...
Pilar
30 days ago
I think we should track adoption rates within Lightning Usage.
upvoted 0 times
...
Daryl
1 months ago
B and C are definitely the right choices here. Tracking the adoption rates and providing the CIO with the details on the migrated functionality is crucial for understanding the success of the transition.
upvoted 0 times
Rasheeda
6 days ago
Agreed, those two options will give the CIO a comprehensive view of the migration success.
upvoted 0 times
...
Tamesha
13 days ago
C) Provide the CIO a list of the User Stories around the new functionality and the Gap Analysis done between Classic and Lightning.
upvoted 0 times
...
Scarlet
18 days ago
B) Track Adoption Rates within the Lightning Usage, and monitor a change in metrics within existing reports and dashboards.
upvoted 0 times
...
...

Save Cancel