MB-280 Exam Preparation Material | Microsoft Dynamics 365 Customer Experience Analyst

Explanation:
Requirement #1
The requirement specifies that sellers want to convert leads gathered at events directly to contacts without necessarily creating opportunities initially.
The Quality lead experience setting in Dynamics 365 allows users to choose which records (Account, Contact, or Opportunity) to create when qualifying a lead.
By enabling this option, users can convert leads to contacts without automatically creating opportunities, aligning with the requirement.
Reference: Microsoft Documentation - Configure Lead Qualification Settings in Dynamics 365
Steps to Configure the Quality Lead Experience Setting:
Navigate to Settings > Administration > System Settings.
Go to the Sales tab.
Set Qualify lead experience to "Yes" to allow flexibility in lead conversion.
Requirement #2
The requirement states that sellers need different options for specifying the final status of deals. The Customize close opportunity form setting allows customization of the form where users specify the status reason when closing an opportunity.
By enabling this, you can provide multiple status options, helping sellers specify various outcomes for closed deals (e.g., different statuses for won or lost deals).
Reference: Microsoft Documentation - Customize Opportunity Close Experience in Dynamics 365
Steps to Configure the Customize Close Opportunity Form Setting:
Navigate to Settings > Administration > System Settings.
Go to the Sales tab.
Set Customize close opportunity form to "Yes" to allow adding specific status options when an opportunity is closed.
By setting these configurations, Dynamics 365 Sales will support both the need for flexible lead qualification and provide detailed status options for opportunity closures, aligning with the organization’s requirements.

Explanation:
Adding Columns to the Active Onboard New Pet View (Option B):
To display the current active stage of the "Onboard new pet" business process flow, you need to ensure that the Active Onboard new pet view includes relevant columns from the Pet table, specifically those tracking process flow stages.
Creating and Adding a New "Onboarding Stage" Column (Option D):
Creating a column such as "Onboarding stage" on the Pet table helps track the active stage of the
onboarding process directly within the view. This allows users to see at a glance which stage each pet
is in without navigating away from the main view.
Other Options:
Option A (Adding a page) refers to modifying the app's navigation, which doesn’t directly impact the visibility of the business process flow stage.
Option C (All Onboard New Pet View) may not be as relevant if you only need to focus on active onboarding records rather than all records.
Reference from Microsoft Documentation:
For configuring views and columns in Dynamics 365, refer to Create and edit views.

Explanation:
Dynamics 365 Sales, Create and activate assignment rules
You can create and manage sequences and assignment rules through navigating to 'Personal Settings' area if users have sequence manager role.



Reference: https://community.dynamics.com/forums/thread/details/?threadid=36a7818d-0ff5-48c8-a9ea-
f9b25d8d9e7e

Explanation:
Correct:
* Transform the first row to be used as headers. Define column types to be the appropriate field types and name the query. Create a full name and full address columns by merging the appropriate columns if they exist. Select Next and your data is now ready for unification.
The proposed solution effectively prepares the data for unification in Dynamics 365 Customer Insights - Data.
Here’s how each step contributes to meeting the goal:
Transform the first row to be used as headers: This step is necessary to define the column names, which is critical for accurate data interpretation.
Define column types to be the appropriate field types: Specifying the correct data types for each column ensures that the data will be processed correctly during unification, maintaining data integrity.
Create a full name and full address columns by merging the appropriate columns if they exist: This step enhances the dataset by consolidating relevant information into single columns, which can simplify data usage and improve data quality. Merging columns helps ensure that users can easily access essential information without navigating through multiple fields.
Select Next: This indicates that the data transformation steps are completed and the dataset is ready for the unification process.
Incorrect:
* Define column types to be appropriate field types and name the query. Create a full name and full address columns by merging the appropriate columns, if they exist. Select Next and your data is now ready for unification.
Does not address the problem with null values.
* Remove any rows where the primary key is missing, delete any leading or trailing zeros on the primary key, and name the query. Select Next and your data is now ready for unification.
Problem not related to the primary key.
* Transform the first row to be used as headers, and remove any special characters or spaces from header row. Remove rows with missing primary keys and name the query. Select Next and your data is now ready for unification.
Does not address the problem with null values.
* Transform the first row to be used as headers, define column types to be the appropriate field types and name the query. Select Next and your data is now ready for unification.
Solution removes all rows with null values, which can lead to significant data loss, especially if those rows contain important information.
It may compromise data quality by eliminating rows, which can impact analysis and insights.
* Transform the first row to be used as headers, remove rows that contain null values, and name the query. Select Next and your data is now ready for unification.
While the solution includes transforming the first row to be used as headers and naming the query, the step of removing rows that contain null values is problematic.
Removing all rows with null values can lead to significant data loss, particularly if those rows contain relevant information.