nerdexam
Microsoft

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

Configure Dynamics 365 Sales standard and premium features

Question

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 instance of Dynamics 365 Sales. Contoso Ltd.'s sellers are becoming accustomed to Copilot in Sales and Sales Insights features. They have identified several desired enhancements. System configuration The base currency for all opportunities in the system is US dollars (USD). The administrator has NOT enabled installed premium Sales Insights features. All users have Premium licenses. Contoso Ltd. uses Exchange Online for email. Only three default insights cards are turned on: 1. Close date coming soon 2. Meeting today 3. Upcoming meeting The system administrator has set the following days before notifying me value for the Close date coming soon card to 21 days. Contoso Ltd. has also just set up Dynamics 365 Customer Insights - Journeys for marketing automation. No segments or customer journeys have been defined yet. Dynamics 365 Sales and Customer Insights - Journeys both share the same instance of Microsoft Dataverse. Copilot in Dynamics 365 Sales settings The following screenshots show the configured fields for opportunity settings summaries and recent changes in Copilot. Contoso Ltd. Personnel Business development managers Contoso Ltd. has 30 business development managers (BDMs) across its sales teams. Each BDM is responsible for selling janitorial services to new and existing clients. All BDMs are assigned the sales manager security role in Dynamics 365 Sales. Any BDM can own an opportunity, even if a different BDM owns the client account record. Any other BDMs assigned to work on the opportunity will be included in the opportunity record's sales team. Opportunity records owned by a BDM will never include any additional client stakeholders other than the named contact for the opportunity. The BDMs have been told to document all client communications in Dynamics 365, but they frequently exchange emails with client contacts through Microsoft Exchange WITHOUT tracking them in Dynamics 365. Digital sales team Contoso Ltd. has a digital sales team that comprises 10 junior sales resources who focus on lead qualification and conversion to opportunities. Members of this team are assigned a single custom security role named Digital seller that is a copy of the standard Salesperson role. View audit history and view audit summary permissions are disabled. The team currently receives leads from an online form on Contoso Ltd.'s website. Many online lead submissions end up being duplicates, and the team manually reconciles the duplicates by comparing last name, email address, and phone number for all submitted leads. Clients Client tiers Clients are grouped into tiers based on annual revenue as calculated in a system outside Dynamics 365 Sales. Clients receive different levels of ongoing service and support based on their tier assignment. Annual revenue values for accounts and corresponding tier values are written to Dynamics 365 through a nightly batch process. Client tier values are only updated when they change, and tier value will always be blank for accounts with no calculated annual revenue. The tier structure is: Tier A -- annual revenue greater than or equal to $10,000,000 USD Tier B -- annual revenue greater than $5,000,000 USD and less than $10,000,000 USD Tier C -- annual revenue greater than $0 USD and less than or equal to $5,000,000 USD The tier label is stored in a custom text field named Client tier (contoso_clienttier) that contains only a single letter or is blank. Northwind Traders account There are three BDMs who frequently work together on large opportunities. BDM1 is the account owner for Northwind Traders, a multinational client. - BDM1 owns all Northwind Traders opportunities with estimated revenue greater than or equal to $1,000,000. BMD2 and BDM3 are assisting BDM1 with several opportunities for Northwind Traders in different cities. - BDM3 owns all other Northwind Traders opportunities. BDM3 is NOT a sales team member for any of the opportunities BDM1 owns. - BDM2 is a sales team member for all Northwind Traders opportunities. Client Contact1 is the primary contact for the Northwind Traders' account. There are two other client contacts with whom the Northwind account team regularly engages - Client Contact2 and Client Contact3. BDM1 and Northwind Traders account BDM1 has been on vacation for two weeks. During vacation, BDM1 did NOT log into Dynamics 365, and BDM2 made the following updates to several open Northwind Traders opportunities. BMD2 also scheduled an internal meeting with BMD1 for the day they return to discuss a request from the primary contact for the account. The meeting has the "London office" opportunity as its regarding value. Desired enhancements The global sales lead requests the following enhancements: 1. A "Welcome" email should be sent to the primary contact for an account when the account first enters any client tier. This email should only be sent to the primary contact once. 2. Account owners should receive immediate notifications in the assistant in Dynamics 365 Sales when accounts change tiers. The notifications should include the account name and current tier. 3. A "Getting started" email should be sent to the main contact associated with an opportunity when the opportunity status is set to "Won." 1. The email should include a link to a custom onboarding form where the contact can supply information required to start the janitorial services for a given location. 2. If the contact does NOT click any links in the email, a follow-up email should be sent. 4. All emails between BDMs and client contacts should be available for relationship analytics KPIs. Emails sent by other users outside of Dynamics 365 should NOT be included in the KPIs. The digital sales team lead requests the following enhancements: 1. The ability for team members to use Copilot to summarize changes to lead records. 2. Replace the current online form used by their team to capture new leads. The new form should automatically handle duplicates using the rules the team currently applies manually. Drag and Drop Question You need to create a custom insight card to display tier change notifications per the global sales lead's request. Which five actions should you perform in sequence? To answer, move the five appropriate actions from the list of actions to the answer area. Arrange the five actions in the correct order. Answer:

Exhibit

MB-280 question #8 exhibit

Answer Area

Drag items

Create a segment-based journey for a segment that includes all primary contacts and accounts where the contoso_clientlier field contains data.Set the frequency to repeat every day.Select the frequency as a one-time journey with a static audience.

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_clienttier field 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_clienttier contains 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.

OptionWhy it fails
Repeat every daySends the Welcome email on a recurring schedule - violates "only sent once"
One-time, static audienceCaptures 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 timeAllows 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

  1. "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.

  2. "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.

  3. "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

#insight cards#Sales Insights assistant#custom notifications#tier change

Community Discussion

No community discussion yet for this question.

Full MB-280 Practice