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

Answer : C

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.

Answer : A

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.

Modifying Status Reasons for Open Opportunities:

The construction company wants to indicate when opportunities are delayed due to specific external factors. To accommodate this, they need specific status reasons like 'Pending Permits' and 'Asbestos Removal.'

By adding these as status reasons under the 'Open' state, you enable sales team members to select these options directly from their current status options.

Steps to Add New Status Reasons to Open Opportunities:

Navigate to Solution: Go to the Dynamics 365 Sales app, then to Settings > Customizations > Customize the System.

Locate the Opportunity Entity: In the default solution, find and expand the 'Entities' list, then select 'Opportunity.'

Edit Statuscode Values: Within the 'Opportunity' entity, select 'Fields,' then find and edit the statuscode field. Here, you can add new options under the 'Open' status. Add 'Pending Permits' and 'Asbestos Removal.'

Publish the Changes: After adding and saving the new status reasons, publish the changes so that they are available to users.

Verifying Custom Status Reason Visibility:

Ensure the new options are available on the Opportunity form for selection.

Test by opening an Opportunity and confirming that the 'Pending Permits' and 'Asbestos Removal' options are available under the Open status reasons.

By following these steps, the sales team can now use specific status reasons to indicate why certain opportunities are delayed, providing clearer visibility into the sales pipeline's status.

Answer : A

To build a trigger-based journey that sends 'Getting started' emails when an opportunity is marked as 'Won,' the appropriate trigger to use is the Dataverse 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:

The Dataverse record change trigger is 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 data and Custom 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 Reference:

Create and manage trigger-based journeys

Work with Dataverse triggers in journeys

By using the Dataverse 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.

Answer : B, C

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 the Sales Copilot user role assigned. 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:

The View Audit History permission 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.

Answer : B, D

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.

Reference from Microsoft Documentation:

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

Answer : A, B

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.

Reference from Microsoft Documentation:

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

Answer : B

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.

Reference from Microsoft Documentation:

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