MB-280 Exam Dumps : Microsoft Dynamics 365 Customer Experience Analyst

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. Thesync to external search indexsetting (Option C) is for integration with external search tools and does not directly impact internal search capabilities.

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

References from Microsoft Documentation:

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

Enable Auditing on Columns (Options A and D):

Enabling auditing on specific columns likeDietary requirementsandEmail addressensures 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 forPetandContact, 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 auditingtracks 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, seeAuditing overview for Dynamics 365.

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 OfficeandToronto Officeare 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 toLondon OfficeandToronto Office.