MB-280 Practice Exam Questions with Answers Microsoft Dynamics 365 Customer Experience Analyst Certification

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.

A white background with black text Description automatically generated

Scenario 1: Adding a New Flavor to the Product Catalog

The bakery develops new bread flavors regularly, and these flavors are variations of an existing product (bread).

In Dynamics 365, product properties are used to define characteristics or options of a product, such as flavors, sizes, or colors. Since the bread flavors are variations, they can be treated as product properties rather than separate products.

By creating a product property, you can add new flavors as options under the existing bread product, allowing flexibility without altering the core product structure.

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

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.

A screenshot of a computer Description automatically generated

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.

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!

Requirement Analysis:

The organization is collecting lead data from two sources: a web form created in Customer Insights - Journeys and manual entries by sales users. This setup could lead to duplicate entries if a lead is submitted through the web form and then entered manually by a sales user afterward.

To ensure data integrity and avoid duplication, it is essential to implement a mechanism that identifies and manages duplicates automatically.

Solution - Enabling Duplicate Detection:

In Dynamics 365, duplicate detection can be configured to alert users or prevent the creation of records that already exist based on certain criteria (such as email).

By enabling duplicate detection based on email addresses, the system will compare incoming lead data with existing records and prompt users if a duplicate is identified. This feature will ensure that leads collected from different sources are not duplicated unnecessarily.

Steps to Enable Duplicate Detection for Leads Based on Email:

Navigate to Settings > Data Management > Duplicate Detection Rules in Dynamics 365.

Create a new Duplicate Detection Rule for the Lead entity. Specify that the system should check for duplicate records based on the email field.

Publish the rule and ensure it is activated.

After activation, this rule will prompt users whenever a duplicate email is detected, either from the Customer Insights - Journeys web form or manual entry by sales users.

? Changing the opportunity to an inactive state allows for the calculation of business process flow duration values, as this state transition prompts the system to finalize any duration metrics associated with the process flow.

? Business process flows calculate duration upon completion or transition of the process, so marking the opportunity as inactive triggers the system to calculate these durations.

Understanding the Base Unit in Dynamics 365 Sales:

In Dynamics 365 Sales, the base unit represents the smallest quantity or measurement used to sell a product or service. It serves as the foundational unit within a unit group, which allows you to define how a product can be measured and sold in various quantities.

All other units within the unit group are defined in relation to this base unit. Therefore, it should represent the smallest quantity possible, ensuring flexibility in defining larger units or multiples based on this standard.

Selecting the Base Unit - Why the Lowest Quantity?

Choosing the lowest needed unit ensures that any other units, whether they are multiples or larger groupings, can be accurately calculated in relation to the base unit. This approach allows you to accommodate various selling quantities and ensures precise calculations across different unit types.

For example, if the lowest unit is a single item, you can then configure units such as a dozen, box, or case based on this base unit. This provides consistency and accuracy in pricing and inventory management.

A screenshot of a computer Description automatically generated

The correct order of actions to enable sales users to view information from custom attributes on leads directly within opportunity records, without navigating to the lead record, is as follows:

Select Tables > Lead.

In the Forms area, create a quick view form with the required columns.

Select Tables > Opportunity.

In the Forms area, select the main form you wish to update.

Add the quick view form as a component.

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

Select Tables > Lead:

Begin by selecting the Lead table, as the attributes that need to be displayed in the Opportunity form originate from the Lead record. This step ensures that you are working with the correct table that holds the data you need.

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.

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. The sync to external search index setting (Option C) is for integration with external search tools and does not directly impact internal search capabilities.

Adding columns 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 to Configure relevance search in Dynamics 365 for more information on indexing tables to enhance search capabilities.

? Since the sales manager wants the Lost column in the forecast to reflect the Total Detail Amount, which is item-driven, you should update the Amount column in the existing forecast layout.

? By editing the existing forecast and changing the source for the Amount column to the Total Detail Amount, you can ensure the forecast accurately reflects item-based revenue calculations without needing to create a new forecast or add calculated columns.

A screenshot of a computer Description automatically generated

The correct order of actions to configure the editing capabilities for the Account records in Copilot for Sales while restricting the "Revenue Forecast" field is as follows:

In Copilot for Sales admin settings, select Forms.

In the settings for the Account table, select Forms.

Select the Account record type.

In the Manage fields section, turn off Allow editing for the "Revenue Forecast" field.

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

In Copilot for Sales Admin Settings, Select Forms:

Start by accessing the admin settings for Copilot for Sales. This is where configuration changes for form accessibility and editing settings are managed. Selecting Forms will allow you to configure specific form-related options for Copilot usage.

In the Settings for the Account Table, Select Forms:

Navigate to the settings for the Account table within Copilot. Selecting Forms at this level allows you to specify which parts of the Account table are editable and visible in Copilot, which directly impacts how users interact with the Account records.

Select the Account Record Type:

Once in the form settings, choose the Account record type that needs to be modified. This is essential for enabling edits to the Account records in Copilot and ensuring that the correct fields are accessible.

In the Manage Fields Section, Turn Off Allow Editing for the "Revenue Forecast" Field:

Finally, within the Manage fields section, disable the Allow editing option specifically for the "Revenue Forecast" field. This action ensures that while Account records can be edited in Copilot, the "Revenue Forecast" field remains read-only, satisfying the requirement from the vice president of sales.

Understanding the Requirement:

The company wants to send push notifications to sellers using the Dynamics 365 Sales mobile app. This requires setting up automated notifications triggered by certain events or conditions.

Solution - Using Cloud Flows:

Cloud flows in Power Automate are ideal for creating automated workflows that can trigger push notifications based on events in Dynamics 365.

Power Automate provides connectors for Dynamics 365 Sales and mobile notifications, enabling the setup of push notifications without requiring custom code or plugins.

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.

? While transforming the first row to be used as headers and defining column types are necessary steps, the solution does not address removing rows with high proportions of nulls. Rows with significant null values can interfere with the quality of the unification process in Customer Insights - Data.

? Therefore, this solution does not fully meet the goal as it does not handle data quality issues caused by null values.

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

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.

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

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.

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