MB-280 Exam Dumps : Microsoft Dynamics 365 Customer Experience Analyst

To build a trigger-based journey that sends "Getting started" emails when an opportunity is marked as "Won," the appropriate trigger to use is theDataverse record change trigger. This trigger is specifically designed to initiate actions based on changes in Microsoft Dataverse records, which are integral to Dynamics 365.

Here’s the detailed reasoning:

Dataverse Record Change Trigger:

TheDataverse record change triggeris used to initiate journeys when there is a change in a record within Dataverse, such as an opportunity's status.

Since the requirement is to send a "Getting started" email once an opportunity status changes to "Won," this trigger can detect the status update in real-time.

Using this trigger, you can specify the criteria for the journey to start, such as filtering for opportunities with a status of "Won," thus automating the email sending based on this condition.

Why Not Other Triggers?

Custom trigger with lead profile dataandCustom trigger with contact profile data:These are generally used for initiating journeys based on custom events or data points outside of standard Dataverse records, which isn’t applicable here as the journey is triggered by an opportunity status change, a native Dataverse record.

Email Link Clicked Interaction Trigger:This trigger is used to follow up after an email link is clicked, which does not align with the scenario. The journey must start based on an opportunity status change, not email interaction.

Microsoft Dynamics 365 References:

Create and manage trigger-based journeys

Work with Dataverse triggers in journeys

By using theDataverse record change trigger, you ensure that the journey aligns directly with the sales process and automatically sends the "Getting started" email when an opportunity reaches the "Won" status, as requested by the global sales lead.

Here’s the correct sequence to configure a new Customer Insights - Journeys form to handle lead duplicates automatically, as per the requirements:

Create a new form:

Start by creating a new form within Customer Insights - Journeys. This is the initial step to set up a form that will capture new leads.

Select a form template:

Choose a template that best fits the purpose of the form. This provides a structure for the form fields and layout, streamlining the setup process.

Set the form target audience to leads:

Since the form will be capturing lead information, specify that the form’s target audience is “leads.” This will ensure that the data is processed and stored as lead records.

Set the form duplicate records strategy to the audience default strategy:

Define how duplicate records are managed. First, apply the default duplicate record strategy for leads. This sets an initial strategy for managing duplicates.

Publish the form:

After completing the setup and configuring the necessary options, publish the form to make it available for use.

Additional Context:

The Create a custom matching strategy and Set the form duplicate records strategy to the custom form matching strategy steps are optional and can be used for further refinement if the default strategy does not meet specific requirements for matching leads based on certain criteria.

By following these steps, you ensure the form is configured for capturing leads and manages duplicates effectively based on the default duplicate record strategy.

Microsoft Dynamics 365 References:

Set up a Customer Insights - Journeys form

Duplicate Detection Rules in Dynamics 365

To enable comprehensive search capabilities for administrators to find all records referencing specific terms (such as “Corgis”), it is essential to ensure that all relevant tables are indexed.

In Dynamics 365, configuring search functionality for specific tables involves setting up the tables to be searchable, which can be done by indexing them within the solution.

Indexing relevant tables makes them accessible in the search feature and ensures all fields within those tables can be searched, allowing for quick retrieval of records that reference specific terms.

System settings(Option A) is limited to selecting up to 10 tables and is more about quick search rather than full indexing. Thesync to external search indexsetting (Option C) is for integration with external search tools and does not directly impact internal search capabilities.

Addingcolumns to the Lookup view(Option D) affects how lookups work but does not influence full-text search results.

References from Microsoft Documentation:

For configuring search indexing, refer toConfigure relevance search in Dynamics 365for more information on indexing tables to enhance search capabilities.