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

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 theActive Onboard new pet viewincludes 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 toCreate and edit views.

? While transforming the first row to be used as headers and defining column types are necessary steps, the solution does not addressremoving 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 doesnot fully meetthe goal as it does not handle data quality issues caused by null values.

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

? When an email is tracked in Dynamics 365 from a delegated mailbox, theprimary mailbox owneris set as the owner of the tracked email. This means that if an assistant sends or tracks an email on behalf of another user, the email’s ownership will reflect the primary mailbox owner rather than the delegate.

? This behavior ensures that activities are correctly associated with the user who owns the mailbox, aligning with the ownership structure in Dynamics 365.

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 forCopilot for Sales. This is where configuration changes for form accessibility and editing settings are managed. SelectingFormswill 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 theAccounttable within Copilot. SelectingFormsat 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 theAccountrecord 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 theManage fieldssection, disable theAllow editingoption 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.

Enable Copilot for Sales in Dynamics 365:

To make Copilot features available, you mustenable Copilot for Sales within Dynamics 365. This involves setting up the environment so that Copilot can access and utilize the sales data effectively.

Verify Server-Side Synchronization and Security Roles:

Copilot for Sales relies onserver-side synchronizationto ensure data flow between Dynamics 365 and other services, such as Teams. Ensure that server-side synchronization is enabled and that users have the necessarysecurity rolesin Dynamics 365 to access and use Copilot.

Assign Privileges for Copilot in Teams:

Ensure that users have the correctprivileges within Teamsto access Copilot. This might involve configuring access policies and permissions so that eligible users can utilize Copilot features during their interactions within Teams.

A screenshot of a computer Description automatically generated

Access Environment Settings in the Power Platform Admin Center:

Start by navigating to thePower Platform Admin Centerwhere environment-specific settings are managed. This is the control center for configuring tracking and other settings for Dynamics 365 instances.

To build a trigger-based journey that sends "Getting started" emails when an opportunity is marked as "Won," the appropriate trigger to use is theDataverse record change trigger. This trigger is specifically designed to initiate actions based on changes in Microsoft Dataverse records, which are integral to Dynamics 365.

Here’s the detailed reasoning:

Dataverse Record Change Trigger:

TheDataverse record change triggeris used to initiate journeys when there is a change in a record within Dataverse, such as an opportunity's status.

Since the requirement is to send a "Getting started" email once an opportunity status changes to "Won," this trigger can detect the status update in real-time.

Using this trigger, you can specify the criteria for the journey to start, such as filtering for opportunities with a status of "Won," thus automating the email sending based on this condition.

Why Not Other Triggers?

Custom trigger with lead profile dataandCustom trigger with contact profile data:These are generally used for initiating journeys based on custom events or data points outside of standard Dataverse records, which isn’t applicable here as the journey is triggered by an opportunity status change, a native Dataverse record.

Email Link Clicked Interaction Trigger:This trigger is used to follow up after an email link is clicked, which does not align with the scenario. The journey must start based on an opportunity status change, not email interaction.

Microsoft Dynamics 365 References:

Create and manage trigger-based journeys

Work with Dataverse triggers in journeys

By using theDataverse record change trigger, you ensure that the journey aligns directly with the sales process and automatically sends the "Getting started" email when an opportunity reaches the "Won" status, as requested by the global sales lead.

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

To enable the digital sales team's request to use Copilot for summarizing changes to lead records, you need to ensure that they have the necessary permissions and access to the required features. Here’s how to proceed:

Assign the Sales Copilot User Role:

Dynamics 365 Copilot in Sales is a feature that assists users by providing insights and summaries based on data within the system.

To allow the digital sales team to access and utilize Copilot's capabilities, they must have theSales Copilot user roleassigned. This role enables users to interact with Copilot and benefit from its AI-driven functionalities such as summarizing changes and insights in records.

Microsoft Documentation Reference:Dynamics 365 Sales Copilot Setup

Grant View Audit History Permissions:

TheView Audit Historypermission is essential for team members to access audit logs, which is necessary for reviewing and summarizing changes made to lead records.

Enabling this permission will allow the digital sales team to view a history of modifications in lead records, thus allowing them to generate summaries based on this audit trail.

The View Audit Summary permission specifically lets them see summaries of audit data, which complements Copilot’s functionality by allowing Copilot to access detailed change history for summarization.

Microsoft Documentation Reference:Security Roles and Privileges

By implementing these two actions, the digital sales team will have both the necessary access to Copilot features and the required permissions to audit lead record changes, enabling them to leverage Copilot for summarizing changes to leads effectively.

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 OfficeandToronto Officeare 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 toLondon OfficeandToronto Office.

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