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 B2B Solution Architect (Arch-301) Exam - Topic 3 Question 56 Discussion

Actual exam question for Salesforce's Salesforce Certified B2B Solution Architect (Arch-301) exam
Question #: 56
Topic #: 3
[All Salesforce Certified B2B Solution Architect (Arch-301) 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


by Victor at Apr 29, 2025, 08:21 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified B2B Solution Architect (Arch-301) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Detra
2 months ago
D is misleading, data won't be the same across platforms!
upvoted 0 times
...
Kayleigh
3 months ago
I disagree, A seems unnecessary. Rolling back is risky.
upvoted 0 times
...
Glory
3 months ago
C sounds good, but is it really enough for the CIO?
upvoted 0 times
...
Junita
3 months ago
Wow, I didn't realize how much was migrated over!
upvoted 0 times
...
Robt
3 months ago
B is a must! Tracking adoption rates is crucial.
upvoted 0 times
...
Lewis
3 months ago
I recall a question similar to this where we had to focus on metrics. Option B definitely stands out as the most relevant for tracking adoption.
upvoted 0 times
...
Michal
4 months ago
I think providing a list of User Stories and Gap Analysis in option C could really help the CIO understand what was migrated. That aligns with what we practiced.
upvoted 0 times
...
Kasandra
4 months ago
I'm not entirely sure about the rollback option in A. It feels risky to allow a complete rollback after such a big migration.
upvoted 0 times
...
Maile
4 months ago
I remember we discussed the importance of tracking adoption rates in our last study group. Option B seems like a solid choice for that.
upvoted 0 times
...
Maryanne
4 months ago
This is a tricky one. I want to make sure I fully understand the requirements before answering. Maybe I'll jot down a quick list of the key things they're looking for first.
upvoted 0 times
...
Providencia
4 months ago
Okay, I think I've got a good strategy here. Tracking adoption rates and providing the gap analysis between Classic and Lightning should give the CIO the visibility they need. I'll make sure to hit those two points.
upvoted 0 times
...
Honey
5 months ago
Hmm, I'm a bit confused about the rollback option. Is that really necessary if the migration was successful? I'll need to think through the pros and cons of that approach.
upvoted 0 times
...
Adolph
5 months ago
This seems like a straightforward question about tracking the migration to Lightning. I'd recommend focusing on the key requirements - adoption rates and what was migrated.
upvoted 0 times
...
Cherrie
9 months ago
Option A is a classic 'easy way out' that the CIO would probably love, but it's not really a sustainable solution. B and C are the practical choices here.
upvoted 0 times
...
Major
9 months ago
Haha, rolling back all the changes? That's like trying to put the toothpaste back in the tube! B and C are the sensible options for sure.
upvoted 0 times
Sue
8 months ago
Haha, rolling back all the changes? That's like trying to put the toothpaste back in the tube! B and C are the sensible options for sure.
upvoted 0 times
...
Elli
8 months 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
...
Adaline
8 months ago
B) Track Adoption Rates within the Lightning Usage, and monitor a change in metrics within existing reports and dashboards.
upvoted 0 times
...
...
William
10 months ago
I don't think we need to roll back all changes. Once we migrate, we should stick with Lightning.
upvoted 0 times
...
Chaya
10 months ago
We should also provide the CIO a list of User Stories and Gap Analysis.
upvoted 0 times
...
Micah
10 months ago
I agree with that. It's important to monitor the change in metrics.
upvoted 0 times
...
Detra
10 months 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
Alita
8 months ago
I'm not sure about option D either. The data should be the same between Classic and Lightning? That doesn't sound accurate to me.
upvoted 0 times
...
Herman
8 months 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
...
Frederic
8 months ago
B) Track Adoption Rates within the Lightning Usage, and monitor a change in metrics within existing reports and dashboards.
upvoted 0 times
...
...
Pilar
10 months ago
I think we should track adoption rates within Lightning Usage.
upvoted 0 times
...
Daryl
10 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
9 months ago
Agreed, those two options will give the CIO a comprehensive view of the migration success.
upvoted 0 times
...
Tamesha
9 months 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
10 months 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