MB-280 · Question #8
Case Study 1 - Contoso Ltd Background information Contoso Ltd. has started a new division that provides janitorial services to businesses. The sales teams for this division are using a dedicated insta
The correct answer is Create a trigger-based journey that triggers on changes to the contoso_clientlier field.; Select the frequency as a one-time journey where newly added members can start at any time.; Add the journey steps.. Explanation: Creating a Tier Change Journey in Customer Insights - Journeys > Note on the question: Despite the title referencing an "insight card," the correct answers are all Customer Insights - Journeys concepts. This question is almost certainly about Enhancement 1 (the Welco
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Create a trigger-based journey that triggers on changes to the contoso_clientlier field.
- Select the frequency as a one-time journey where newly added members can start at any time.
- Add the journey steps.
Explanation
Explanation: Creating a Tier Change Journey in Customer Insights - Journeys
Note on the question: Despite the title referencing an "insight card," the correct answers are all Customer Insights - Journeys concepts. This question is almost certainly about Enhancement 1 (the Welcome email sent once when an account first enters a tier), not Enhancement 2. The journey triggers on the
contoso_clienttierfield change, which aligns with the Welcome email requirement.
Correct Arrangement & Why
Step 1: Create a trigger-based journey that triggers on changes to the contoso_clienttier field
Why this goes first and why trigger-based (not segment-based):
The requirement is to react to a specific data event - the moment a tier value is written for the first time. A trigger-based journey fires in response to a record attribute changing, making it the right tool for "when an account first enters any client tier."
A segment-based journey (distractor) is wrong because:
- Segments are evaluated on a schedule, not in real-time
- A segment like "accounts where
contoso_clienttiercontains data" would include all accounts that already have tiers - not just newly tiered ones - It's designed for mass broadcasts to pre-defined audiences, not reactive, event-driven flows
Step 2: Select the frequency as a one-time journey where newly added members can start at any time
Why this specific frequency (not the other two options):
The requirement states the email should be sent only once, and new accounts will continuously enter tiers over time.
| Option | Why it fails |
|---|---|
| Repeat every day | Sends the Welcome email on a recurring schedule - violates "only sent once" |
| One-time, static audience | Captures only members who qualify at journey launch - misses every account that gets a tier after the journey starts |
| One-time, newly added members can start at any time | Allows future accounts to enter the journey when they first get a tier, but each contact only traverses it once |
"Newly added members can start at any time" is the key phrase - it keeps the journey open-ended so it works for accounts tiered today and accounts tiered six months from now.
Step 3: Add the journey steps
Why this is last:
You can only configure what the journey does (send email, add conditions, set wait times) after you've established the journey type and audience entry rules. The journey framework must exist before you populate it with actions.
Common Misconceptions
-
"Segment-based is fine because a segment can filter new tiers" - Segments don't fire on field changes; they evaluate membership periodically. You'd miss the real-time trigger requirement and likely spam already-tiered accounts.
-
"One-time static audience is safe because the journey only runs once" - "Static" means the member list is frozen at journey publication. Any account that gets its first tier after that moment is excluded entirely.
-
"Repeat daily ensures everyone gets notified" - This would send the Welcome email every day to every tiered account, which is both incorrect behavior and a potential compliance/annoyance issue.
Topics
Community Discussion
No community discussion yet for this question.
