Salesforce Rev-Con-201 Exam - Topic 1 Question 1 Discussion

Actual exam question for Salesforce's Rev-Con-201 exam

Question #: 1
Topic #: 1

On the final day of User Acceptance Testing (UAT), a critical issue is discovered. The tester believes the critical issue is a bug, while the developer asserts it is working as designed. The business representative suspects a training issue, and the project manager views the critical issue as scope creep.

What is the next course of action to mitigate this critical issue?

AAll involved parties should review the issue, cross-referencing against the approved business requirements, and collaboratively determine if it is a legitimate defect, a training gap, or a new requirement.

BEscalate the issue to the steering committee and request an exception to deploy the solution as is; given that it is the final day of UAT, there is no time remaining for further review.

CThe consultant should review the critical issue, perform root cause analysis, reproduce the issue in the development sandbox, fix it to maintain the go-live date, and deploy it to UAT.

Show Suggested Answer

Suggested Answer: A

In Salesforce Revenue Cloud implementations, especially during User Acceptance Testing (UAT), it is common to encounter discrepancies in expectations versus system behavior. When stakeholders disagree on the nature of a critical issue --- whether it is a defect, scope change, or training gap --- the correct course of action is to collaboratively review the issue against the signed-off business requirements.

Per the Salesforce Implementation Best Practices, a triage meeting or working session involving the tester, developer, business stakeholder, and project manager should be conducted to:

Review the documented business requirements and use cases

Evaluate whether the issue represents a missed requirement, a misunderstanding, or a training need

Reach consensus on how to classify and resolve the issue

Option A reflects this structured and collaborative approach.

Option B is premature escalation without due diligence and can lead to bypassing quality assurance.

Option C assumes the issue is a bug and skips the critical validation and stakeholder agreement process, risking scope deviation or misalignment.

Exact Extracts from Salesforce Revenue Cloud Documents:

Salesforce Partner Implementation Guide -- ''Managing UAT and Defect Triage'':

''Conduct issue triage sessions with key stakeholders to determine if findings are bugs, enhancements, or training gaps. Always align resolution path with documented requirements.''

Revenue Cloud Delivery Framework -- ''Final UAT and Go-Live Readiness'':

''Do not assume issue type. Instead, validate all critical issues with documentation and team consensus.''

Salesforce Partner Implementation Guide

Revenue Cloud Delivery Framework

Salesforce Project Governance and UAT Checklist

by Veronika at Nov 19, 2025, 08:56 AM

Limited Time Offer

25%

Off

Get Premium Rev-Con-201 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Val

3 days ago

C seems risky. We can't just fix things on the fly like that!

upvoted 0 times

...

Olene

8 days ago

Wait, how can we be sure it's just a training issue? Sounds fishy to me.

upvoted 0 times

...

Lucina

13 days ago

I'm leaning towards A too. We need to ensure everyone is on the same page.

upvoted 0 times

...

Bernadine

18 days ago

Totally disagree, we can't waste time on this. Let's just go with B.

upvoted 0 times

...

Allene

24 days ago

I think option A makes the most sense. We need to clarify what's really going on.

upvoted 0 times

...

Sheldon

29 days ago

Haha, I bet the project manager is just hoping it's "scope creep" so they don't have to deal with it.

upvoted 0 times

...

Freeman

1 month ago

Option C is tempting, but the consultant shouldn't just fix it and deploy without proper review. That's a recipe for disaster.

upvoted 0 times

...

Lillian

1 month ago

I feel like option C could lead to more problems later on. Rushing a fix without proper analysis might just create more bugs down the line.

upvoted 0 times

...

Shalon

1 month ago

I practiced a similar question where we had to decide between fixing a bug or addressing training issues. I think option A aligns with that scenario.

upvoted 0 times

...

Delmy

2 months ago

I'm not entirely sure, but I think escalating to the steering committee might just delay things even more. It feels risky to go that route.

upvoted 0 times

...

Kasandra

2 months ago

I'm leaning towards option A. Even though it might take some time, I think it's important to get everyone on the same page and make sure we're addressing the real issue, whether it's a bug, training, or scope creep. Rushing into a fix without understanding the root cause could lead to bigger problems down the line.

upvoted 0 times

...

Weldon

2 months ago

Reviewing the requirements and collaborating to find the right solution sounds like the most thorough approach, but I'm concerned it might take too long at this stage. Maybe a mix of options A and C could work?

upvoted 0 times

...

Desirae

2 months ago

I agree with option A. Rushing to deploy without fully understanding the issue could lead to bigger problems down the line.

upvoted 0 times

...

Nadine

2 months ago

I remember we discussed the importance of collaboration in UAT, so option A seems like the best approach to clarify the issue.

upvoted 0 times

...

Beatriz

3 months ago

Option A seems like the most reasonable approach. Getting all stakeholders involved to review the issue and determine the root cause is the best way to resolve this.

upvoted 0 times

...

Theola

3 months ago

Option B? Are you kidding me? Escalating to the steering committee on the final day of UAT? That's a surefire way to get laughed out of the room.

upvoted 0 times

...

Tammara

3 months ago

Hmm, I'm not sure. With the deadline looming, I'm worried that taking the time to review everything might delay the go-live. Maybe we should just push it through and deal with any fallout later.

upvoted 0 times

...

Loreta

3 months ago

I think the best approach here is to get all the key stakeholders together to review the issue and the requirements. That way we can determine the root cause and the appropriate next steps.

upvoted 0 times

Belen

3 months ago

Let’s cross-reference with the business requirements.

upvoted 0 times

...