Microsoft MB-220 common mistakes
Microsoft MB-220 · Understand the traps and how to avoid them.
Treating segments as live queries that reflect new data instantly, and promising a stakeholder that a contact added minutes ago will be in the next journey run.
Candidates study segment creation as a form-filling exercise and skim over the distinction between static and dynamic segments and how dynamic segments refresh on a schedule rather than on every record change.
What to do instead
Learn which segment types exist, that dynamic segments are refreshed by a system process rather than instantly, and that a static segment only changes when records are added or removed explicitly. Be able to explain how to force a refresh and why a journey bound to a dynamic segment sees the membership at the time the segment was last evaluated.
Designing a journey that sends a follow-up email two days after a trigger, then assuming every contact who qualifies on day one receives it on day three regardless of journey state.
Candidates memorise journey tiles visually but never reason about how the journey's time zone setting, the contact's time zone, and the tile's delay interact, so they misjudge send times.
What to do instead
Work through the send-time logic: a delay tile waits the specified duration from the previous step, while a time-of-day or time-zone setting can shift the actual send. Practise calculating the delivery time for a contact in a different time zone from the journey's default and confirm which setting wins.
Assuming a lead is automatically promoted to a contact with all fields mapped when a marketing form is submitted, without configuring or checking the matching and mapping behaviour.
The lead-to-contact flow feels obvious, so candidates skip the configuration screens that decide whether a new lead is created, an existing lead is updated, or a contact is created, and they miss the field mapping step.
What to do instead
Study the form submission outcome options and the lead matching rules, including which field is used to match and what happens on a match versus no match. Know where field mapping between form fields and lead or contact fields is defined and how to test the result after a submission.
Building an email with a personalisation token that resolves to blank for some recipients and concluding the token system is broken, rather than checking the source field and fallback.
Candidates learn the syntax for inserting dynamic content but not the dependency on the underlying record field being populated or the existence of a default value.
What to do instead
Verify that the referenced field exists on the target entity, is populated for the audience, and has a fallback configured where the editor allows it. Test with a small seed segment containing a record with the field empty to confirm the fallback renders instead of an empty string.
Configuring an event and then wondering why registrants never receive the confirmation, because the registration journey was never linked or the event's registration response was not enabled.
Events are studied as a standalone set of forms and sessions, and the connection between the event record, the registration form, and the journey that handles confirmation is easy to overlook.
What to do instead
Map the end-to-end event flow: create the event, define sessions and passes, build the registration form, then connect a journey that triggers on registration and sends confirmation and reminders. Confirm which trigger the journey uses and test a registration to see whether the journey enrols the registrant.
Changing an email's content after a journey has gone live and expecting the change to apply to contacts already inside the journey, without republishing or checking the customer journey state.
Candidates treat live journeys like editable documents and do not distinguish between draft, live, and stopped states or the effect of editing a dependent record.
What to do instead
Learn which edits require stopping and restarting a journey, which edits propagate automatically, and how versioning of emails and journeys behaves. Practise the safe pattern: stop the journey, edit and publish the asset, then create a new version or restart so that in-flight contacts are handled predictably.
Assuming every contact receives every marketing email unless they unsubscribe, ignoring consent, do-not-email flags, and subscription centre choices.
Candidates focus on the send action and skip the preference and consent model, so they cannot explain why a contact was suppressed from a send.
What to do instead
Study the consent model in use, the meaning of the do-not-email and blocked fields, and how subscription centres record topic-level preferences. Be able to trace a suppressed contact through consent, preference, and suppression list checks to identify which one blocked the send.
Creating a segment with an attribute condition that references a related entity and getting no results, then rebuilding the segment from scratch instead of diagnosing the relationship path.
The segment builder's natural-language style hides the underlying query, and candidates do not realise that related-entity conditions require a defined relationship and correct traversal.
What to do instead
Learn to switch to the advanced query view to inspect the generated query, confirm the relationship exists and is the correct direction, and test the condition against a single known record. Use the segment member preview or test records to isolate whether the condition or the relationship is at fault.
Setting up a marketing form hosted on an external site and finding submissions never appear, because the form capture or posting configuration was incomplete.
Candidates conflate hosted forms with form capture and do not realise that an external page needs the form's posting mechanism wired to the correct endpoint and fields mapped.
What to do instead
Distinguish between a hosted marketing form and a captured external form, and know that capture requires embedding the generated script or posting to the form's endpoint with matching field names. Validate by submitting a test entry and confirming the submission appears against the right contact or lead.
Assuming a lead scored above the threshold automatically converts to a qualified opportunity, rather than only triggering the configured action.
Scoring models are studied as a numbers exercise, and candidates do not connect a score change to the model's configured threshold action, which may be a journey trigger rather than a record update.
What to do instead
Study how a scoring model defines positive and negative conditions, how the threshold is set, and what action fires when the threshold is crossed. Know that the typical pattern is a trigger that enrols the lead in a journey, and that the actual qualification step is a separate action you must configure.