Download Microsoft Dynamics 365 Customer Experience Analyst.MB-280.VCEplus.2025-02-27.31q.vcex

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.

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 DocumentationReference: Dynamics 365 Sales Copilot SetupGrant 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 PrivilegesBy 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.

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.

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 365Reference:Create and manage trigger-based journeysWork with Dataverse triggers in journeysBy 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.