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

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.

A screenshot of a computer Description automatically generated

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.

A white background with black text Description automatically generated

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.

A white background with black text Description automatically generated

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

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.

A close up of a text Description automatically generated

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.

A screenshot of a computer AI-generated content may be incorrect.

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.

A screenshot of a chat AI-generated content may be incorrect.

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.

A screenshot of a phone Description automatically generated

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.

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.

Understanding the Requirement:

The company needs to apply a separate flat rate discount for preferred customers on specific products. This discount varies depending on the customer’s country or region.

A Discount List in Dynamics 365 Sales is used to apply specific discounts on products under defined conditions.

Solution - Creating a Discount List:

A Discount List can be tailored to preferred customers and configured to apply discounts based on specific products and customer attributes, such as their country or region.

Using a Discount List ensures flexibility and control over the discount structure, allowing the organization to manage regional variations in pricing for preferred customers.

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.

Understanding the Statuscode and Statecode Columns:

In Dynamics 365 Sales, opportunities have two primary columns related to their status: statecode and statuscode.

The statecode defines the primary state of an opportunity (e.g., Open, Won, Lost).

The statuscode provides more granular reasons associated with each primary state. For example, within the "Open" state, you can have various reasons such as "In Progress," "On Hold," etc.

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.

 Creating a flow to update the Status Reason of the business process flow table record to "Finished" and the Status to "Inactive" upon opportunity closure ensures that the business process flow is marked as complete. This triggers the calculation of duration values.

 This solution explicitly handles the process completion state, which guarantees that the business process flow duration is recorded even if the opportunity is won prematurely.

To display the active stage of the business process flow (BPF) in the Pet table view, the active stage must be stored in a column within the Pet table. Since the Onboard new pet BPF is linked to the Pet table, a cloud flow can be used to fetch the active stage from the BPF and write it into a newly created column on the Pet table.

Once the data is available in the Pet table, the next step is to modify an existing view. Since the Active Pets view is already being used in the system, modifying this view by adding the newly created column ensures that the relevant data is visible. Saving the edited view as a new one and sharing it with the founder completes the requirement.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

The configurations in the Salesperson security role will determine the access and visibility the carer has to the "Corgi meet-up" business process flow. The carer should be able to view and interact with specific business process flows on the Pet records based on the permissions configured by the founder.

Business Process Flow Access Configuration:

The image shows that the "Salesperson" security role has the "Create," "Read," "Write," "Delete," "Append," and "Append To" permissions set for the "Corgi meet-up" process.

The green circle indicates permissions at the Organization level, meaning the carer can access all records associated with the "Corgi meet-up" business process flow across the entire organization.

Visibility of Business Process Flows on Pet Records:

Since the carer has these permissions at the Organization level, they will be able to see all business process flows related to pet records that have been set up by the founder.

In this case, the answer provided in the image indicates that the carer will be able to see business process flows that were created by both the founder and new flows initiated by the carer themselves on the Pet records.

Switch Process Dialog Visibility:

The switch process dialog will allow the carer to select from multiple business process flows that are applicable to a given record.

According to the selection options provided, if both the "Corgi meet-up" and the "Onboard new pet" flows are available, and they are configured to be accessible by the Salesperson role, the carer should be able to see both flows when using the switch process dialog. This aligns with the provided answer choices, which indicate that both flows are visible when switching.

References from Microsoft Documentation:

Microsoft’s official documentation on configuring Security Roles in Dynamics 365 provides detailed guidance on setting permissions for different entities and processes. More information can be found in the Dynamics 365 security model documentation: Manage security, users, and teams

For Business Process Flow configurations, including permissions and visibility settings, refer to the guide on Create a business process flow in Dynamics 365.

This setup ensures that the carer has the appropriate level of access to perform their duties, specifically in handling pet records and business processes like the "Corgi meet-up."

If you have further questions or need more details on this configuration, feel free to ask!

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.

 To assign salespeople to sales territories, the user needs permissions to manage territory assignments, which is typically a higher-level responsibility.

 The Vice president of sales role includes privileges related to managing sales territories, unlike the Sales team member or Salesperson roles, which are more focused on direct sales tasks.

 The System customizer role does not specifically grant territory management permissions and is more focused on customization and configuration tasks.

 In Dynamics 365, business process flows are limited to 30 stages across all entities within a single process. Since each entity here (Lead, Opportunity, Quote, Order, Invoice) has 10 stages, the total would be 50 stages, exceeding the limit.

 To meet the requirements, you need to reduce the total number of stages to comply with this limitation. Reducing the total number of steps per stage, tables, or steps won’t directly address the stage limit issue.

Product families allow you to group related products under a common category, making it easier for the sales team to navigate and find products within the same category, such as all versions of flat-screen TVs.

By using Product families, you can organize products into a hierarchical structure that reflects their categorization, enabling sales users to browse and select items more efficiently within Dynamics 365 Sales.