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 CRT-101 Topic 6 Question 54 Discussion

Actual exam question for Salesforce's CRT-101 exam
Question #: 54
Topic #: 6
[All CRT-101 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Olen
1 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
1 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
Latonia
4 days ago
A) Reduce the number of case status values to five.
upvoted 0 times
...
...
Abraham
1 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
5 days 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
12 days 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
27 days ago
A) Reduce the number of case status values to five.
upvoted 0 times
...
...
Hester
2 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
Dierdre
10 days 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
11 days ago
A) Reduce the number of case status values to five.
upvoted 0 times
...
Nieves
12 days 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
27 days 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
1 months ago
A) Reduce the number of case status values to five.
upvoted 0 times
...
...
Blondell
2 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
Geoffrey
1 months ago
D) Edit the status choices directly on the record type.
upvoted 0 times
...
King
1 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
...
Rachael
1 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
...
Alton
2 months ago
A) Reduce the number of case status values to five.
upvoted 0 times
...
...
Alana
2 months ago
I prefer option B. Creating a Screen Flow would make it easier for service reps to select the correct status values.
upvoted 0 times
...
Madonna
2 months ago
I agree with Huey. Having different support processes for each record type makes sense.
upvoted 0 times
...
Huey
2 months ago
I think option C is the best choice. It allows for customization based on record type.
upvoted 0 times
...

Save Cancel