Practice Free MB-280 Microsoft Dynamics 365 Customer Experience Analyst Exam Questions Answers With Explanation

Renaming the Omitted Column to Cancelled:

To rename a column in the forecast layout, such as changing Omitted to Cancelled, you should go to Layout column settings. This setting allows you to customize how columns appear in the forecast view, including renaming columns to better match your business terminology.

Renaming within Layout column settings will directly change how this column is labeled in the user interface for clarity and consistency with business terms.

Show As

Visualize this view

To catch up on scheduled tasks and activities, BDM1 can use specific features in the Dynamics 365 Sales Hub interface. Here’s how they work in this scenario:

Show As:

The " Show As " option allows users to change the view of their current page. BDM1 can use this feature to switch to a timeline or agenda view, which can help display upcoming activities, tasks, and reminders in a format that may highlight pending actions, like the meeting scheduled by BDM2.

When in the appropriate view, reminder cards for tasks and meetings can surface based on relevance and priority.

Visualize this view:

The " Visualize this view " option helps BDM1 to see an overview of upcoming tasks, scheduled meetings, and associated records in a graphical format.

This visualization can be particularly useful for identifying key upcoming events like the meeting BDM2 scheduled, as it provides a clear summary of upcoming activities, aiding in prioritization and catch-up efforts.

Microsoft Dynamics 365 References:

Using assistant cards in Dynamics 365 Sales

Configuring views and visualizations in Dynamics 365

By selecting these options, BDM1 can effectively access and view the assistant card related to the scheduled meeting, facilitating a quick catch-up on all pending activities.

The correct order of actions to set up a product catalog, including the ability for sellers to apply quantity discounts, is as follows:

Create units.

Add products.

Create price lists.

Add price list items.

Create discount lists.

Create Units:

Start by defining units (e.g., each, box, dozen) for your products. Units specify how products are measured and sold, which is essential for setting pricing and discounts.

This step ensures that all products have consistent units of measure before adding them to the catalog.

Date Field - Actual End:

The Actual End date field is typically used to mark when an activity, such as an outgoing call, is completed. Since the sales manager wants to measure completed outgoing calls, using Actual End ensures that only calls finished within the fiscal year are included in the goal measurement.

This setting will align with the requirement to track activities finished within a specific time frame (January - December).

BDM2 is a contact of interest for ? both the London Office and Toronto Office opportunities.

BDM2 is a sales team member for all Northwind Traders opportunities, meaning they are involved in both the London Office and Toronto Office opportunities.

BDM3 is a contact of interest for ? the Toronto Office opportunity.

BDM3 owns all Northwind Traders opportunities except those owned by BDM1. Since BDM1 owns the London Office opportunity, BDM3 is only involved in the Toronto Office opportunity.

Client Contact2 is a contact of interest for ? the Toronto Office opportunity.

The Toronto Office opportunity lists Client Contact2 as the primary contact, making them a contact of interest for that opportunity.

Client Contact1 is a contact of interest for ? the London Office opportunity.

The London Office opportunity lists Client Contact1 as the primary contact, making them a contact of interest for that opportunity.

Requirement #1 Explanation:

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.

Requirement Analysis:

The goal is to include only specific opportunities—those that " sell " —in the forecast. This requires the ability to selectively include opportunities that meet specific criteria, such as the status, stage, or type of sale.

Solution - Using Additional Filters:

In Dynamics 365 Sales, additional filters can be applied within the forecast configuration to refine the opportunities included. Filters allow you to specify criteria such as opportunity status, probability, estimated revenue, or any custom field that signifies the opportunity has " sold. "

By setting up filters, you can ensure that only opportunities matching the desired criteria are included in the forecast, providing a targeted and accurate view of expected sales.

Steps to Configure Additional Filters in Forecasting:

Go to Sales > Forecasts, and select or create a new forecast.

In the forecast settings, navigate to Filters and add conditions that define which opportunities are included. For example, you can filter based on status (e.g., only include opportunities marked as " Won " ).

Save and apply the filter settings to ensure only the relevant opportunities appear in the forecast.

Retail assistant - Salesperson

The retail assistant can create and update accounts and contacts but cannot edit the product catalog. The Salesperson role provides access to manage accounts and contacts but does not include permissions for product catalog management.

Executive - Sales team member

The executive only adds notes to accounts and contacts. The Sales team member role has minimal access and is appropriate for a user who only needs to add notes.

Territory manager - Sales manager

The territory manager is responsible for forecasting and product management, which aligns with the Sales manager role, as it includes permissions for managing forecasts and overseeing sales activities.

In Dynamics 365 Sales, security roles control access to different forms, views, and records. To ensure that each department can only access their respective custom forms and views, you should assign security roles to the forms and views. This allows you to restrict users based on their department so they only see the forms and views relevant to them.

How it works:

Edit the form properties ? Assign the form to specific security roles.

Edit the view properties ? Restrict views based on security roles.

Ensure users have the correct security roles ? Users in Department A will only see their assigned forms and views, and the same applies to Department B.

? In Dynamics 365 Sales, currency exchange rates are applied to opportunity records when specific triggers occur. These exchange rates are updated manually on a periodic basis (e.g., once a month) to reflect current currency values.

? Exchange rates are recalculated for an opportunity when there is a change in the status reason (e.g., from open to won or lost). This trigger ensures that the most recent exchange rate is used when key changes occur in the opportunity lifecycle, maintaining accurate currency reporting.

The timeline control in Dynamics 365 allows users to view and interact with activities, notes, and posts associated with a record. To meet Terra Flora’s requirements for displaying specific activities, you need to customize the timeline to show only certain activity types.

Removing All Other Activity Types Except Task, Email, and Phone Call (Option B):

According to Terra Flora ' s requirements, only Tasks, Emails, and Phone Calls should appear in the timeline for Pet records. Therefore, removing all other activity types ensures that only the relevant activities are shown. This customization is achieved in the timeline settings by unchecking unnecessary activity types.

Unchecking the Posts Option (Option C):

Since Terra Flora specified that posts should not appear on the timeline, you should uncheck the Posts option under the Record types settings in the timeline configuration. This action removes posts from the view, aligning with Terra Flora’s requirement to exclude posts from the Pet records timeline.

Other Options Explanation:

Unchecking Notes (Option A) would prevent users from adding or viewing notes, which Terra Flora requires.

Unchecking the Activities Option (Option D) would disable all activities on the timeline, which does not meet Terra Flora’s needs as they require Task, Email, and Phone Call activities.

Option E deals with the display format of notes but does not restrict their visibility, which does not align with the requirement to exclude posts specifically.

References from Microsoft Documentation:

For configuring and customizing the timeline control, refer to Customize a timeline control in Dynamics 365 documentation for detailed steps on modifying timeline settings and activity visibility.

Requirement: Add the Type of Loss

To track reasons for lost opportunities, including specifics like losses to competitors, you need to provide additional details on why an opportunity was closed as lost.

The Status Reason field can be customized to include specific reasons for the loss. This field is used within the context of the Opportunity entity and allows the addition of options to detail specific loss types.

By modifying the Status Reason option set, you can add various reasons (like " Lost to Competitor " ) which will appear as options when closing an opportunity as lost.

Configure table relationship cascading behavior

The CascadeConfiguration class or CascadeConfiguration complex type) contains the properties representing actions that may be performed on the referenced table in the one-to-many relationship. Each property can be assigned one of the values of the CascadeType enum type.

* Restrict

Prevent the Referenced table record from being deleted when referencing tables exist.

Incorrect:

* Cascade All

Perform the action on all referencing table records associated with the referenced table record.

* Cascade Active

Perform the action on all active referencing table records associated with the referenced table record.

* Remove Link

Remove the value of the referencing column for all referencing table records associated with the referenced table record.

To identify duplicate records, you need to configure both duplicate detection rules and duplicate detection jobs.

Since Terra Flora requires identifying duplicate pet records across various fields, creating three duplicate detection rules is likely necessary to cover different columns (such as name, breed, and dietary requirements) in the Pet table.

One duplicate detection job is sufficient to run these rules concurrently, scanning the database for duplicates across the specified columns. This job can be scheduled or run manually.

Option B is correct as it ensures comprehensive coverage with three rules addressing various fields and one job to manage the duplicate detection process.

References from Microsoft Documentation:

For guidance on setting up duplicate detection jobs and rules, refer to Detect duplicate records in Dynamics 365.

? Since the company uses Microsoft SharePoint for document storage, access to documents is controlled through SharePoint permissions rather than Dynamics 365 security roles.

? To restrict document access to only the contracts team, you should update the users list in the SharePoint site where the documents are stored. This involves configuring SharePoint permissions to ensure that only the contracts team (or a specific SharePoint group associated with them) has access to the document library where contracts are stored.

Enable Auditing on Columns (Options A and D):

Enabling auditing on specific columns like Dietary requirements and Email address ensures that any changes to these fields are tracked. This meets Terra Flora ' s requirement to log changes to these fields along with details of who made the changes and the timestamp.

Enable Auditing on Pet and Contact Tables (Options B and C):

By enabling auditing at the table level for Pet and Contact, you ensure that any updates to these tables, including changes to all associated columns, are recorded. This broad setting ensures full coverage of auditing for both tables.

Enable Audit User Access (Option F):

This option is recommended to track when users access certain data, which can help with compliance and monitoring user interactions with sensitive data.

Option E (Start Read Auditing):

Read auditing tracks when records are read. If compliance requires monitoring every time a record is accessed, enabling this could be necessary; however, the primary focus is on modifications rather than access alone.

References from Microsoft Documentation:

For setting up auditing, see Auditing overview for Dynamics 365.

The correct order of actions to create a new custom account plan table with a hierarchical parent-child relationship visualization is as follows:

Create a new account plan table.

Create a 1

self-referential relationship and mark the relationship as hierarchical.

Open the advanced Relationship settings.

Go to the Hierarchy Settings grid view.

Step by Step Comprehensive Detailed Explanation with ALL Microsoft Dynamics 365 References:

Create a New Account Plan Table:

To model account plans for subsidiaries and manage the parent-child relationships, start by creating a new table (entity) named " Account Plan. "

This table will store information related to the account plans, and you can define custom fields and settings as needed.

The correct order of actions to create a sequence of tasks and assign them to lead records based on the same criteria as assignment rules is as follows:

Create a sequence.

Add tasks to the sequence.

Connect the existing segment to the sequence.

Activate the sequence.

Create a Sequence:

Start by creating a sequence in Dynamics 365 Sales. A sequence is a defined set of steps (tasks) that are applied to records in a systematic manner. It helps automate the task creation process based on predefined criteria.

In Dynamics 365 Sales, unit groups define how products are sold in different quantities. The base unit is the smallest unit of measure in a unit group. Since customers now want to buy widgets individually, the smallest unit (Each) should be set as the base unit for all other units (Box, Case, and Pallet).

Correct:

* Recalculate the forecast

Incorrect:

* Recalculate the opportunity.

* Update the Opportunity Forecast Category Mapping process.

Open the Opportunity Forecast Category Mapping Process workflow. You can customize or deactivate the workflow according to your organization ' s requirements.

Note:

Example of forecast recalculation methods

Let ' s understand the different methods with an example. Consider a scenario where you have a forecast with 4 quarterly periods and an annual period. Assume that you ' re currently in Q4. The following table shows when and how the forecast data is updated for different scenarios and periods.

--

Dynamics 365 Sales, Recalculate forecasts manually

You want the forecast data to be up-to-date to make informed decisions. Forecast data is automatically recalculated at regular intervals. However, you can trigger a manual recalculation when you want to recalculate the forecast data immediately. You can also trigger a manual recalculation for past and future periods as they aren ' t automatically recalculated.

Recalculate and refresh forecast data manually

1. Open the forecast. Verify the Last updated timestamp on the command bar to know when the forecast was last recalculated successfully.

2. Select Recalculate data.

A notification appears at the top of the screen, confirming the recalculation. Recalculation happens in the background, and you can continue to work while recalculation is in progress.

3. After the application recalculates the forecast data, a notification appears to refresh the data. On the notification, select Refresh page.

First Name, Last Name, and Business Unit must be match in both filter.

Additionally Preferred Phone in one of the filters.

Also Email in the other filter.

Correct:

* : From the email settings in the Advanced settings, you migrate email router data from server-side synchronization to Dynamics 365 app for Outlook. [See step 1 below. Use Server-side synchronization]

* You test the email configuration and enable the mailboxes for the Dynamics 365 App for Outlook designated users. [Yes, see step 2 below]

Incorrect:

* Within the system settings and email configuration, you set Process Email Using to Dynamics 365 for Outlook. [No, set this to Server-side synchronization. See step 1 below]

Note:

Deploy and install Dynamics 365 App for Outlook

Step 1: Set the default synchronization method

To use Dynamics 365 App for Outlook, you need to set server-side synchronization for your email processing.

1. From your app, go to Settings > Advanced Settings.

2. Go Settings > Administration and then select System Settings.

3. Select the Email tab, and set Process Email Using to Server-Side Synchronization.

Step 2: Test email configuration and enable mailboxes

Enable and test your user mailboxes so they can use Dynamics 365 App for Outlook.

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

Define a forecast model

Define the entities that must be used to generate the forecast.

1. In the General step of the Forecast configuration page, define the fields that should be used for the forecast.

[Steps 2 to 6 omitted]

7. Select a Rollup to hierarchy relationship.

This step establishes a relationship between the rollup and hierarchy entities. Each forecast template starts with a default rollup to hierarchy relationship:

Choose different values to support your organization ' s specific requirements if needed.

Note: Select a template

The fastest way to create a forecast is to use a template. The template that you select defines how the forecast groups data.

On the Forecast configurations page, select one of the following templates:

Org chart forecast: Rollup columns and projections are based on your organization ' s reporting structure. This template uses the Manager field of the User entity for the hierarchy.

Product forecast: Rollup columns and projections are based on the product hierarchy.

*- > Territory forecast: Rollup columns and projections are based on the sales territory hierarchy.

In Dynamics 365 Marketing, when creating an email for a campaign, certain required fields must be completed before the email can be saved. The From Address is essential because it specifies the sender of the email, which is necessary for email configuration. The Subject is also required, as it defines the email ' s purpose and is a mandatory field for email setup.