Quick Answer
The correct answer is frequency capping, because this journey setting directly limits how many times a customer can re-enter or receive communications from the same journey within a defined time window. In Dynamics 365 Customer Insights - Journeys, when a customer meets a trigger condition—such as not having made a purchase in 30 days—they can be re-triggered repeatedly if no cap is set, causing them to receive the same discount offer multiple times. Frequency capping prevents this by enforcing a maximum entry count per customer, ensuring each person only receives the offer once during the specified period. On the MB-910 exam, this concept tests your understanding of journey optimization settings and is often paired with a distractor like “segment refresh rate” or “trigger conditions,” which control who enters but not how often. A common trap is confusing frequency capping with suppression segments; remember that frequency capping is about repetition limits, not exclusion lists. Memory tip: think “cap the repeat” to recall that frequency capping stops customers from looping back into the same journey.
This MB-910 practice question tests your understanding of describe dynamics 365 customer insights. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company uses Dynamics 365 Customer Insights - Journeys. They have a journey that sends a discount offer to customers who have not made a purchase in 30 days. They notice that some customers are receiving the offer multiple times. Which journey setting should they modify?
Entity
Why wrong: Entity defines the target audience object, not frequency.
Goal
Why wrong: Goal defines success, not frequency.
Schedule
Why wrong: Schedule controls timing, not frequency of entry.
Frequency capping
Frequency capping limits how many times a customer can enter the journey or receive communications.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Frequency capping
Frequency capping is the correct setting because it limits how many times a customer can enter or receive communications from a journey within a specified period. In Dynamics 365 Customer Insights - Journeys, this prevents customers who meet the trigger condition (e.g., no purchase in 30 days) from being re-entered into the same journey repeatedly, which is the root cause of receiving the offer multiple times.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Entity
Why it's wrong here
Entity defines the target audience object, not frequency.
Goal
Why it's wrong here
Goal defines success, not frequency.
Schedule
Why it's wrong here
Schedule controls timing, not frequency of entry.
Frequency capping
Why this is correct
Frequency capping limits how many times a customer can enter the journey or receive communications.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often confuse 'Schedule' (which controls when the journey runs) with the mechanism that prevents individual contacts from being re-entered, not realizing that frequency capping is a separate, contact-level suppression setting.
Detailed technical explanation
Frequency capping in Dynamics 365 Customer Insights - Journeys is configured at the journey level under 'Other settings' and can be set to limit the number of times a contact can enter the journey (e.g., once every 30 days). Under the hood, the system uses a suppression window tied to the contact's journey participation history, which is checked against the journey's entry trigger to prevent re-entry. In a real-world scenario, without frequency capping, a customer who consistently fails to purchase every 30 days could be re-entered each time the journey runs, leading to the exact duplicate offer issue described.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Describe Dynamics 365 Customer Insights — study guide chapter
Learn the concepts, then practise the questions
Describe Dynamics 365 Customer Insights practice questions
Targeted practice on this topic area only
All MB-910 questions
977 questions across all exam domains
Microsoft Dynamics 365 Fundamentals CRM MB-910 study guide
Full concept coverage aligned to exam objectives
MB-910 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise MB-910 questions linked to Describe Dynamics 365 Customer Insights.
Practise MB-910 questions linked to Describe Dynamics 365 Sales.
Practise MB-910 questions linked to Describe Dynamics 365 Customer Service.
Practise MB-910 questions linked to Describe Dynamics 365 Field Service.
Practise MB-910 questions linked to Explore the core capabilities of customer engagement apps in Dynamics 365.
Practise MB-910 questions linked to Describe shared features and Copilot capabilities.
Practise MB-910 questions linked to MB-910 fundamentals.
Practise MB-910 questions linked to MB-910 scenario.
Practise MB-910 questions linked to MB-910 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Describe Dynamics 365 Customer Insights — This question tests Describe Dynamics 365 Customer Insights — Read the scenario before looking for a memorised answer..
The correct answer is: Frequency capping — Frequency capping is the correct setting because it limits how many times a customer can enter or receive communications from a journey within a specified period. In Dynamics 365 Customer Insights - Journeys, this prevents customers who meet the trigger condition (e.g., no purchase in 30 days) from being re-entered into the same journey repeatedly, which is the root cause of receiving the offer multiple times.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
This MB-910 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-910 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.