Microsoft MB-280 Practice Test - Questions Answers, Page 2

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.

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.

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.

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.

When determining the primary table in Customer Insights during the unification process, the goal is to choose the table that provides the most robust and accurate customer profile information.

Criterion A is crucial because having complete and reliable customer profile data ensures that the unified profile is accurate and comprehensive.

Criterion C is recommended by Microsoft when using Dynamics 365 data, as the contact table often serves as the primary source of customer information within the Dynamics 365 ecosystem.

While tables with many related tables or common attributes with other tables may provide supplementary information, they do not necessarily constitute the primary source for reliable customer data.

The Query Assist feature in Dynamics 365 Customer Insights - Journeys utilizes natural language processing to help marketers easily build segments.

By using simple language, marketers can describe their target audience without needing to know complex query syntax, making segmentation more accessible.

This feature is designed to streamline segment creation, allowing marketers to quickly define their audience with natural language inputs, which is particularly useful for users who may not be familiar with technical query building.