Microsoft MB-280 Microsoft Dynamics 365 Customer Experience Analyst Exam Practice Test

Since a child site within the existing SharePoint site collection has been renamed, the best approach is to update the relative URL in Dynamics 365 Sales. The relative URL defines the path within the parent site and must match the new name to ensure document management continues to function correctly.

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 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).

In Dynamics 365 Customer Insights - Data, primary key attributes must uniquely identify records and be consistent across the data source.

Whole Number and GUID are commonly used data types for primary keys because they can uniquely identify records and are natively supported for primary keys in databases.

String can also be used as a primary key if it uniquely identifies each record (e.g., an email address).

Integer and Boolean are generally not used as primary keys in Customer Insights because they may not provide unique identifiers suitable for all scenarios.

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.

Correct:

* Recalculate the forecast

Incorrect:

* Recalculate the opportunity.

* Update the Opportunity Forecast Category Mapping process.

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.

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.

 To make a new table, like Locations, visible within the Sales Hub, you need to add it to the App Designer. This involves updating the Sales Hub app module to include the Locations table as a new entity that users can access.

 By adding the table in the App Designer, you ensure it becomes part of the navigation and is available within the Sales Hub application.

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.

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.

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.

Delete: Currently set to " Cascade All, " which is causing the issue of deleting the pet records when the Contact record is deleted. This should be changed to " Restrict " to prevent deletion if related Pet records exist.

Reparent: Since any active bookings should be updated when the Pet ' s primary owner is reassigned, the Reparent option should be set to " Cascade Active " instead of " Cascade All " to ensure that only active bookings are updated, not inactive ones.

Dynamics 365 Sales uses the Opportunity Sales Access Team template to provide access to the opportunity record to all the users connected under the Sales team connection role category. A salesperson who might not have access to a given opportunity record by their assigned security role privileges can still get access when added as a sales team member from this subgrid. This allows the sales team member users to access and work with the opportunity record in Dynamics 365 on a per-record basis. Similarly, when an existing sales team member is deleted from the subgrid, the access to the opportunity record granted via the access team template is also removed.

Note: Use access teams and owner teams to collaborate and share information

When to use access teams

The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren’t provided.

The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.

A unique set of users requires access to a single record without having an ownership of the record.

Correct:

* After you save a Power Query data source, you have to manually trigger the initial refresh process.

* You can add additional tables to the data source using Get Data functionality in the Power Query.

Incorrect:

* After you save a Power Query data source, you have to manually trigger the initial refresh process.

* You can only add additional columns to the dataset in Power Query before the data source is created in Customer Insights - Data.

* You must create a separate Power Query data source for each table you wish to ingest.

Note:

* After you save a Power Query data source, you have to manually trigger the initial refresh process.

For Power BI users, refreshing data typically means importing data from the original data sources into a semantic model, either based on a refresh schedule or on demand. You can perform multiple semantic model refreshes daily, which might be necessary if the underlying source data changes frequently.

* You can add additional tables to the data source using Get Data functionality in the Power Query.

When using Power Query in Dynamics 365 Customer Insights - Data, you have the flexibility to add additional tables to your data source through the Get Data functionality. This allows you to manage multiple tables and sources efficiently within a single Power Query environment.

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.

 In Dynamics 365 Customer Insights - Data, when using Power Query to ingest data, the Get Data functionality allows users to add multiple tables from various data sources.

 This flexibility enables users to enrich the dataset by pulling in additional tables that may be related or necessary for the data unification process.

 Power Query in Customer Insights supports creating robust data flows by allowing multiple tables to be added within a single data source setup, providing a comprehensive data modeling environment.

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.

References from Microsoft Documentation:

For configuring views and columns in Dynamics 365, refer to Create and edit views.

To update the Opportunity Close form in Dynamics 365 Sales, you need a role that allows modification of system entities, including the Opportunity entity and its associated forms. The System administrator role provides full access to all customization features in Dynamics 365, including modifying forms, fields, and layouts.

To display a custom image (such as an .svg file) as an icon for a table in a model-driven app, the image should be uploaded as a web resource in Dynamics 365. Web resources are used to store images, scripts, and other assets that can be referenced within the application.

Once uploaded as a web resource, the image can be set as the table icon in the customization settings of the Pet table.

Determine the Price of the Product Bundle: Use the lunch bundle price

Since the lunch bundle is predefined at $200.00, the price for the bundle should be set using the lunch bundle price. This ensures that any associated products (Sandwich, Napkins, and Soda) are automatically included in this price, simplifying the process for the sales staff.

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.

1. Create a trigger-based journey that triggers on changes to the contoso_clienttier field.

Since the " Welcome " email should be sent when an account first enters any client tier, a trigger-based journey is required. The trigger should activate when the contoso_clienttier field is updated with a value.

2. Select the frequency as a one-time journey where newly added members can start at any time.

A one-time journey with newly added members ensures that each new primary contact will enter the journey when their account first gets assigned a tier.

3. Add the journey steps.

After defining the journey type and trigger, the necessary email steps (sending the " Welcome " email) must be added before publishing.

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.

1. Create a Power Automate flow with a Dataverse " When a row is added, modified or deleted " trigger.

This ensures that the flow is triggered when an account ' s client tier changes.

2. Set the table and column conditions for the triggering event.

The trigger should monitor changes to the contoso_clienttier field in the Accounts table.

3. Add a step to call the " Create card for assistant " action.

This step ensures that a custom insight card is created for the assistant in Dynamics 365 Sales.

4. Save and test the flow by manually performing an update.

This verifies that the Power Automate flow is correctly detecting tier changes and triggering the insight card.

5. Update the insight card item to select the flow.

This ensures that the newly created insight card is linked to the correct Power Automate flow.

Opportunity Updated Today is Not Included in the Chart: Update roll-up settings

The roll-up settings control how frequently the data is aggregated and included in the goal metrics. If an opportunity updated today is not appearing, it likely indicates that the roll-up process has not yet captured the recent data change.

By updating the roll-up settings, you can adjust the frequency or manually trigger an update, ensuring that all recent updates are reflected in the chart.

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.

BDM1 has a reminder setting for close dates that are coming up within the next 21 days, as configured in the system. Given that BDM1 logs in on June 3, 2024, here’s how to determine which opportunities will be highlighted in the " Close date coming soon " reminder cards:

Calculate the Reminder Period:

With a 21-day notification period, any opportunities with close dates on or before June 24, 2024 (21 days from June 3), will trigger a reminder card in the assistant.

Evaluate Close Dates for Opportunities:

London Office: Scheduled to close on June 4, 2024, which is within 21 days from June 3.

Toronto Office: Scheduled to close on June 12, 2024, which also falls within the 21-day reminder period.

Mexico City Office: Scheduled to close on June 18, 2024, within the 21-day reminder period.

Seattle Office: Scheduled to close on June 19, 2024, also within the 21-day period.

Based on this, London Office and Toronto Office are within the specified period and thus will appear as close date reminders for BDM1.

Microsoft Dynamics 365 References:

Assistant and Insights cards in Dynamics 365 Sales

By applying the specified close date threshold, we can confirm that the reminder cards for opportunities closing on June 4 and June 12 will be displayed to BDM1, which corresponds to London Office and Toronto Office.