Microsoft MB-280 Practice Test - Questions Answers

In the Forms Area, Create a Quick View Form with the Required Columns:

Within the Lead table, go to the Forms section and create a Quick View form. The Quick View form will be designed to include the necessary custom attributes from the Lead table.

This step is crucial as the Quick View form will later be embedded in the Opportunity form to provide context about the originating lead.

Select Tables > Opportunity:

After configuring the Quick View form in the Lead table, navigate to the Opportunity table where you will embed this Quick View form.

In the Forms Area, Select the Main Form You Wish to Update:

Within the Opportunity table, go to the Forms area, and select the Main Form that sales users will use. This is where you will add the Quick View form created from the Lead table.

Add the Quick View Form as a Component:

Finally, add the previously created Quick View form as a component on the Opportunity Main Form. This will enable the embedded display of lead information, allowing users to view lead data directly within the Opportunity form.

Once added, save and publish the form to make the changes effective.

By following these steps, sales users can access lead information within the Opportunity form itself, streamlining their workflow by removing the need to navigate to the Lead record.

Understanding the Requirement:

The company needs to apply a separate flat rate discount for preferred customers on specific products. This discount varies depending on the customer's country or region.

A Discount List in Dynamics 365 Sales is used to apply specific discounts on products under defined conditions.

Solution - Creating a Discount List:

A Discount List can be tailored to preferred customers and configured to apply discounts based on specific products and customer attributes, such as their country or region.

Using a Discount List ensures flexibility and control over the discount structure, allowing the organization to manage regional variations in pricing for preferred customers.

Steps to Create a Discount List for Preferred Customers:

Navigate to Settings > Product Catalog > Discount Lists.

Create a new Discount List and specify criteria for preferred customers.

Add discount values for the specific products and set conditions based on regions or countries as needed.

Save and publish the Discount List for it to be available for quotes.

By using a Discount List, the company can apply specific discounts to preferred customers while taking into account regional pricing variations, providing a tailored and efficient solution for quote management.

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

Steps to Create a Cloud Flow for Push Notifications:

Go to Power Automate and create a new Cloud Flow.

Set up a trigger based on a Dynamics 365 event (e.g., when a record is created or updated).

Add an action to send a push notification to the user's mobile device.

Customize the notification message and publish the flow to activate the notifications.

Using Cloud Flows in Power Automate enables dynamic push notifications for mobile users, providing timely updates to sales team members based on real-time data changes.

Add Tasks to the Sequence:

After creating the sequence, add the specific tasks that need to be automatically generated and assigned to the leads. These tasks can be calls, follow-ups, emails, etc., that need to be completed as part of the sales process.

Connect the Existing Segment to the Sequence:

Once the tasks are added, connect the sequence to the existing segment that filters the lead records based on assignment rules. This ensures that only leads within this specific segment are targeted by the sequence.

The segment is a subset of leads that meet certain criteria, and connecting it to the sequence allows for automated task assignment according to the segment's filtering rules.

Activate the Sequence:

Finally, activate the sequence to begin the automated assignment of tasks to lead records that meet the segment criteria. Activation makes the sequence live, enabling the automated process to assign tasks to each lead as per the sequence setup.

By following these steps, the sales manager can ensure that tasks are automatically generated and assigned to leads according to the same criteria used by the assignment rules, streamlining task management for the sales team.

To enable comprehensive search capabilities for administrators to find all records referencing specific terms (such as ''Corgis''), it is essential to ensure that all relevant tables are indexed.

In Dynamics 365, configuring search functionality for specific tables involves setting up the tables to be searchable, which can be done by indexing them within the solution.

Indexing relevant tables makes them accessible in the search feature and ensures all fields within those tables can be searched, allowing for quick retrieval of records that reference specific terms.

System settings (Option A) is limited to selecting up to 10 tables and is more about quick search rather than full indexing. The sync to external search index setting (Option C) is for integration with external search tools and does not directly impact internal search capabilities.

Adding columns to the Lookup view (Option D) affects how lookups work but does not influence full-text search results.

Reference from Microsoft Documentation:

For configuring search indexing, refer to Configure relevance search in Dynamics 365 for more information on indexing tables to enhance search capabilities.

The timeline control in Dynamics 365 allows users to view and interact with activities, notes, and posts associated with a record. To meet Terra Flora's requirements for displaying specific activities, you need to customize the timeline to show only certain activity types.

Removing All Other Activity Types Except Task, Email, and Phone Call (Option B):

According to Terra Flora's requirements, only Tasks, Emails, and Phone Calls should appear in the timeline for Pet records. Therefore, removing all other activity types ensures that only the relevant activities are shown. This customization is achieved in the timeline settings by unchecking unnecessary activity types.

Unchecking the Posts Option (Option C):

Since Terra Flora specified that posts should not appear on the timeline, you should uncheck the Posts option under the Record types settings in the timeline configuration. This action removes posts from the view, aligning with Terra Flora's requirement to exclude posts from the Pet records timeline.

Other Options Explanation:

Unchecking Notes (Option A) would prevent users from adding or viewing notes, which Terra Flora requires.

Unchecking the Activities Option (Option D) would disable all activities on the timeline, which does not meet Terra Flora's needs as they require Task, Email, and Phone Call activities.

Option E deals with the display format of notes but does not restrict their visibility, which does not align with the requirement to exclude posts specifically.

Reference from Microsoft Documentation:

For configuring and customizing the timeline control, refer to Customize a timeline control in Dynamics 365 documentation for detailed steps on modifying timeline settings and activity visibility.

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.