Microsoft MB-280 Exam Questions

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.

When an email is tracked in Dynamics 365 from a delegated mailbox, the primary mailbox owner is set as the owner of the tracked email. This means that if an assistant sends or tracks an email on behalf of another user, the email's ownership will reflect the primary mailbox owner rather than the delegate.

This behavior ensures that activities are correctly associated with the user who owns the mailbox, aligning with the ownership structure in Dynamics 365.

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.

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.

Manager on System User Record:

Suggested contacts in Teams can include users directly linked to the individual starting the chat. The manager assigned on the user's system record can be a suggested contact, as this is a common relationship that suggests frequent communication.

Record Owner of the Initiating Record:

The owner of the record being discussed or acted upon is also likely to be a suggested contact. This is because the owner has primary responsibility for the record and would commonly need to be consulted or informed about actions related to it.

Created By of the Initiating Record:

If the user is the Created By for a record, they are associated with its initial setup or creation. As a result, they may be suggested when actions on that record are taken since they are familiar with its origins.

These selections align with the rules typically used for suggesting contacts in integrated Teams chats, ensuring relevant parties are automatically suggested based on record associations and user relationships.