Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam MB-220 Topic 3 Question 80 Discussion

Actual exam question for Microsoft's MB-220 exam
Question #: 80
Topic #: 3
[All MB-220 Questions]

You work for a non-profit organization where donations are registered and managed within the same Microsoft Power Apps environment where Dynamics 365 Customer Insights - Journeys is enabled and used. The donation table has a direct link to a contact record. When people cancel a donation, a reason is added through an option list.

When a donation is cancelled and becomes deactivated, the donation team wants to trigger a real-time journey to send a confirmation and call-to-action for a single donation. To accomplish this, you work with the donation team and create the journey and a Microsoft Dataverse trigger for the donation table. However, there are some cancellation reasons that are NOT applicable and should NOT be included in the journey.

You need to ensure that certain cancellation reasons are excluded and do NOT start a customer journey.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Theodora
12 days ago
Option B is the way to go. Exclusion segments are the unsung heroes of customer journeys.
upvoted 0 times
...
Tasia
14 days ago
Ah, the joys of dealing with donation management. At least it's not as complex as herding cats, right?
upvoted 0 times
...
Catalina
25 days ago
I wonder if Option A would work, but it might get messy if you have a lot of different cancellation reasons to filter. Better to keep it simple.
upvoted 0 times
...
Hailey
29 days ago
Option D seems a bit too much of a workaround. Why not just use the Cancellation Reason field as it was intended?
upvoted 0 times
Penney
14 days ago
D) On the Dataverse trigger, set the attribute that activates the trigger to the Status field instead of the Cancellation Reason field.
upvoted 0 times
...
Lilli
15 days ago
C) Add an attribute tile in the real-time journey. Add filter conditions with the applicable cancelation reasons. Only add the email tile to the applicable branch.
upvoted 0 times
...
Nicholle
16 days ago
B) Create an exclusion segment of contacts that have donations with specific cancelation reasons. Add this segment to the real-time journey as an excluded segment.
upvoted 0 times
...
Tarra
19 days ago
A) In the creation step of the customer journey, add filter conditions to specify which cancellation reasons it should run on.
upvoted 0 times
...
...
Hyman
2 months ago
I like how Option C allows you to filter the journey based on the cancellation reason. That way, you can have more control over the process.
upvoted 0 times
Beckie
17 days ago
D) On the Dataverse trigger, set the attribute that activates the trigger to the Status field instead of the Cancellation Reason field
upvoted 0 times
...
Melvin
19 days ago
C) Add an attribute tile in the real-time journey. Add filter conditions with the applicable cancelation reasons. Only add the email tile to the applicable branch.
upvoted 0 times
...
Katy
20 days ago
B) Create an exclusion segment of contacts that have donations with specific cancelation reasons. Add this segment to the real-time journey as an excluded segment.
upvoted 0 times
...
Donette
26 days ago
A) In the creation step of the customer journey, add filter conditions to specify which cancellation reasons it should run on.
upvoted 0 times
...
...
Eden
2 months ago
I agree with Valene. Option A) seems like the best way to ensure only certain cancellation reasons start the customer journey.
upvoted 0 times
...
Valene
2 months ago
I think we should go with option A) and add filter conditions to specify which cancellation reasons should trigger the journey.
upvoted 0 times
...
Cristal
2 months ago
Option B sounds like the most straightforward approach. Excluding the specific cancellation reasons from the journey seems like the cleanest solution.
upvoted 0 times
Florinda
1 months ago
That way, we can ensure that the journey only triggers for the relevant cancellation reasons.
upvoted 0 times
...
Gwenn
1 months ago
It definitely makes sense to create an exclusion segment for those specific reasons.
upvoted 0 times
...
Dona
2 months ago
I agree, option B seems like the best way to exclude certain cancellation reasons from the journey.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77