Salesforce CRT-101 Exam - Topic 6 Question 54 Discussion

Actual exam question for Salesforce's CRT-101 exam

Question #: 54
Topic #: 6

Universal Containers is trying to improve the user experience when searching for the tight status on a case. The company currently has one support process that is used for all record types on cases. The

support process has 10 status values. Service reps say they never need more than five depending on what kind of case they are working on.

How should the administrator improve on the current implementation?

AReduce the number of case status values to five.

BCreate a Screen Flow that shows only the correct values for status and surface the flow in the utility
bar of the console.

CReview which status choices are needed for each record type and create support processes for each
that is necessary.

DEdit the status choices directly on the record type.

Show Suggested Answer

Suggested Answer: A

by Theola at Apr 24, 2023, 09:55 AM

Limited Time Offer

25%

Off

Get Premium CRT-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Truman

4 months ago

A Screen Flow could make it easier for reps to find what they need!

upvoted 0 times

...

Haydee

4 months ago

Wait, are they really using all 10 status values? Seems excessive!

upvoted 0 times

...

Floyd

4 months ago

Definitely need to review status choices for each record type.

upvoted 0 times

...

Alesia

4 months ago

I disagree, having more options can help clarify cases.

upvoted 0 times

...

Rozella

4 months ago

Reducing to five status values sounds efficient!

upvoted 0 times

...

Gianna

5 months ago

Editing the status choices directly on the record type seems too simplistic. I think we need a more structured approach, but I can't quite remember the details.

upvoted 0 times

...

Susy

5 months ago

I feel like we practiced a question similar to this where we had to create different support processes for different record types. That might be the best way to handle the varying needs.

upvoted 0 times

...

Anthony

5 months ago

I think creating a Screen Flow could help streamline the process, but I can't recall if it would actually limit the options based on the case type.

upvoted 0 times

...

Sharika

5 months ago

I remember we discussed how having too many status values can confuse users, so reducing them to five might be a good idea. But I'm not sure if that's the best approach for all cases.

upvoted 0 times

...

Laurel

5 months ago

I think I've got a good handle on this. The key is to identify the actions that demonstrate the vendor's attention to detail and compliance with the assessment process.

upvoted 0 times

...

Merlyn

5 months ago

This seems like a straightforward question about Salesforce features. I'll need to think through the differences between the options to determine the best one for ensuring testability across environments.

upvoted 0 times

...

Olen

9 months ago

Option A? Really? Reducing the status values to five? Might as well just have one status: 'It's broken, good luck!'

upvoted 0 times

...

Roslyn

10 months ago

Option D is just asking for trouble. Directly editing the status choices on the record type? That's a recipe for a maintenance nightmare waiting to happen.

upvoted 0 times

Oliva

8 months ago

C) Review which status choices are needed for each record type and create support processes for each that is necessary.

upvoted 0 times

...

Brandon

8 months ago

B) Create a Screen Flow that shows only the correct values for status and surface the flow in the utility bar of the console.

upvoted 0 times

...

Latonia

9 months ago

A) Reduce the number of case status values to five.

upvoted 0 times

...

Abraham

10 months ago

Option B is an interesting idea, but it might be overkill for this scenario. A simple Screen Flow could be a bit of a bandaid solution when you can just create the right support processes.

upvoted 0 times

Kristel

9 months ago

B) Create a Screen Flow that shows only the correct values for status and surface the flow in the utility bar of the console.

upvoted 0 times

...

Otis

9 months ago

C) Review which status choices are needed for each record type and create support processes for each that is necessary.

upvoted 0 times

...

Fletcher

9 months ago

A) Reduce the number of case status values to five.

upvoted 0 times

...

Hester

10 months ago

I agree with Blondell. Customizing the support processes for each record type is the way to go. No need to shoehorn everything into a one-size-fits-all approach.

upvoted 0 times

Florinda

8 months ago

C) Review which status choices are needed for each record type and create support processes for each that is necessary.

upvoted 0 times

...

Dierdre

9 months ago

B) Create a Screen Flow that shows only the correct values for status and surface the flow in the utility bar of the console.

upvoted 0 times

...

Van

9 months ago

A) Reduce the number of case status values to five.

upvoted 0 times

...

Nieves

9 months ago

C) Review which status choices are needed for each record type and create support processes for each that is necessary.

upvoted 0 times

...

Janessa

9 months ago

B) Create a Screen Flow that shows only the correct values for status and surface the flow in the utility bar of the console.

upvoted 0 times

...

Dalene

10 months ago

A) Reduce the number of case status values to five.

upvoted 0 times

...

Blondell

11 months ago

Option C seems like the most comprehensive solution. Tailoring the support processes to each record type will provide a more targeted and efficient experience for the service reps.

upvoted 0 times