MB-280 Sample Questions Answers

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.

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

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.

 Using the Close as Won dialog without completing the business process flow does not ensure that the business process flow duration is calculated. The process flow needs to be marked as completed or transitioned to an inactive state for duration values to be captured.

 Simply closing an opportunity as won without completing the flow may bypass the finalization of process flow metrics, hence the goal is not met in this case.

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.

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.

 In Dynamics 365 Sales, currency exchange rates are applied to opportunity records when specific triggers occur. These exchange rates are updated manually on a periodic basis (e.g., once a month) to reflect current currency values.

 Exchange rates are recalculated for an opportunity when there is a change in the status reason (e.g., from open to won or lost). This trigger ensures that the most recent exchange rate is used when key changes occur in the opportunity lifecycle, maintaining accurate currency reporting.

 Since the company uses Microsoft SharePoint for document storage, access to documents is controlled through SharePoint permissions rather than Dynamics 365 security roles.

 To restrict document access to only the contracts team, you should update the users list in the SharePoint site where the documents are stored. This involves configuring SharePoint permissions to ensure that only the contracts team (or a specific SharePoint group associated with them) has access to the document library where contracts are stored.

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

Delete: Currently set to " Cascade All, " which is causing the issue of deleting the pet records when the Contact record is deleted. This should be changed to " Restrict " to prevent deletion if related Pet records exist.

Reparent: Since any active bookings should be updated when the Pet ' s primary owner is reassigned, the Reparent option should be set to " Cascade Active " instead of " Cascade All " to ensure that only active bookings are updated, not inactive ones.

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.

References from Microsoft Documentation:

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

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.

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.

In Dynamics 365 Marketing, when creating an email for a campaign, certain required fields must be completed before the email can be saved. The From Address is essential because it specifies the sender of the email, which is necessary for email configuration. The Subject is also required, as it defines the email ' s purpose and is a mandatory field for email setup.

To ensure that newly added wine enthusiasts automatically receive the marketing email, the segment must dynamically update based on contact data. Using Automatic Refresh, the system continuously updates the segment whenever new contacts meet the specified criteria (wine order history and location in Europe). This ensures that all qualifying contacts, including those added after the segment was initially created, are included in the marketing journey.

Enable Copilot for Sales in Dynamics 365:

To make Copilot features available, you must enable 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 on server-side synchronization to ensure data flow between Dynamics 365 and other services, such as Teams. Ensure that server-side synchronization is enabled and that users have the necessary security roles in Dynamics 365 to access and use Copilot.

Assign Privileges for Copilot in Teams:

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

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.

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.

Update All User Mailboxes to Sync with Exchange Online:

Since your organization has moved from Gmail to Exchange Online, the first step is to update the mailbox settings for each user to enable synchronization with Exchange Online. This change in configuration aligns with the new email server settings, allowing Dynamics 365 to handle email via Microsoft Exchange Online instead of Gmail.

This step ensures that user mailboxes are correctly configured to communicate with the new Exchange environment.

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.

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.

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