MB-280 無料問題集「Microsoft Dynamics 365 Customer Experience Analyst」

You use opportunities in Dynamics 365 Sales.
Opportunities that were closed as lost frequently come back and are eventually won.
You need to be able to track these occurrences and have insight into the process.
What happens during the reopen and close process? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
正解:

Explanation:
An organization is using Microsoft Power Query when connecting to data sources in Dynamics 365 Customer Insights - Data. You need to load contacts to Customer Insights - Data using Power Query. Which is an appropriate action to take when using Power Query to ingest data?

解説: (JPNTest メンバーにのみ表示されます)
A company has two departments. Each department uses only custom forms and views designed for each department. Currently, all users can view all forms and views.
The company wants to improve usability for its users.
You need to limit users to only individual department forms and views.
What should you do?

解説: (JPNTest メンバーにのみ表示されます)
A bakery uses Dynamics 365 Sales. All loaves of bread sold at the bakery are priced the same. Special bread flavors are developed regularly.
You need to add a new flavor to the product catalog.
What should you do for each scenario? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
正解:

Explanation:

* 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.
Reference: Microsoft Documentation - Define Product Properties in Dynamics 365 Steps to Create a Product Property:
Go to Sales > Product Catalog > Products.
Open the existing product (bread) and navigate to Product Properties.
Add a new property (flavor) and define the possible values (e.g., new flavors).
Save and publish the product with the updated properties.
Scenario 2: Changing an Order to a New Bread Flavor in an Opportunity
When a customer wants to change their order to a new flavor within an existing opportunity, the selected product in the opportunity can be updated to reflect the new flavor.
Since flavors are configured as product properties, you can select the specific flavor for the opportunity product directly without needing to recreate or delete the product from the opportunity.
This approach leverages product properties, ensuring that the change is streamlined and does not require re- adding or modifying the core product.
Reference: Microsoft Documentation - Configure Products in Opportunities in Dynamics 365 Steps to Select a New Flavor in the Opportunity Product:
Open the specific opportunity record in Dynamics 365.
Navigate to the product line items and select the bread product.
In the product properties, update the flavor to the new option as required.
Save the changes to ensure the opportunity reflects the new flavor selection.
These actions allow the bakery to manage new flavors flexibly within their product catalog and seamlessly adjust opportunities to accommodate flavor changes, enhancing customer satisfaction and operational efficiency.
A company manually assigns leads to salespeople.
The sales manager requires automated lead assignment rules. An administrator enables the feature. However, you are unable to access the Assignment rules area.
You need to request access from the administrator.
Which security role should you request?

解説: (JPNTest メンバーにのみ表示されます)
A company is using Dynamics 365 Sales to track their sales pipeline.
Sales managers require their forecasting to include reasons why opportunities were lost, including losses to competitors.
You need to configure the sales process WITHOUT using custom code.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
正解:

Explanation:

* 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.
Reference: Microsoft Documentation - Customize Status Reasons for Opportunities Steps to Modify the Status Reason Option Set:
Go to Settings > Customizations > Customize the System.
Locate the Opportunity entity and open its Fields section.
Find and select the statuscode (Status Reason) field.
Add new options to represent specific loss types and save the changes.
Publish the customization to make the new Status Reason options available for users.
Requirement: Record the Loss for Forecasting
Sales managers need to include lost opportunities and their reasons in forecasting. To ensure that this information is captured accurately, modifying the Opportunity Close form will allow users to specify details when marking an opportunity as closed (won or lost).
By customizing the Opportunity Close form, you can include fields that capture detailed information required for forecasting, such as the type of loss and any competitor information. This ensures that loss details are available for analysis and forecasting without needing custom code.
Reference: Microsoft Documentation - Customize Opportunity Close Experience in Dynamics 365 Steps to Modify the Opportunity Close Form:
In the Sales Hub, navigate to App Settings > Close Opportunity Experience.
Customize the Opportunity Close form to include fields that are relevant to capturing loss information, such as adding fields for competitors or reasons.
Save and publish the form to reflect the changes.
By modifying the Status Reason option set and customizing the Opportunity Close form, you enable the sales team to record detailed reasons for lost opportunities, which will support accurate forecasting and analysis, all without using custom code.
New
A company is implementing the Dynamics 365 Sales mobile app.
The company requires setup of several push notifications for sellers who use the app.
You need to create the push notifications.
Which feature should you use?

解説: (JPNTest メンバーにのみ表示されます)
Your organization has been noticing some peculiar field changes on certain records and wants to know what is causing this. You need to audit user access and updates for several custom tables.
Which two boxes must be checked as prerequisites steps? To answer, select the appropriate check boxes in the answer area. NOTE: Each correct selection is worth one point.
正解:

* Start Auditing:
* Enabling Start Auditing is the primary step to activate auditing for Dynamics 365. This setting ensures that changes to data, including field updates on records, are tracked and logged.
* Without enabling this checkbox, no data changes will be recorded, as it is the fundamental requirement for auditing across all entities and fields.
Reference: Microsoft Documentation - Enable and Configure Auditing in Dynamics 365 Audit User Access:
The Audit User Access checkbox ensures that user activities related to accessing records are tracked. This is essential for identifying when specific users accessed records, which could correlate with field changes observed.
Enabling this option provides insights into who accessed which records and when, which is useful in understanding user behavior and any unusual access patterns.
Reference: Microsoft Documentation - Configure User Access Auditing
Additional Steps for Table-specific Auditing (if needed):
After enabling auditing at the system level, specific tables (entities) need to have auditing enabled if they are not covered under common, sales, marketing, or customer service entities.
Go to Settings > Customizations > Customize the System, select the custom table, and ensure that Auditing is enabled on the desired fields within the table.
By enabling both Start Auditing and Audit User Access, you ensure that both data changes and access patterns are recorded, providing a comprehensive audit trail for monitoring and troubleshooting field changes on records.

弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

オンラインサポート時間:( UTC+9 ) 9:00-24:00
月曜日から土曜日まで

サポート:現在連絡