Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam MS-700 Topic 10 Question 85 Discussion

Actual exam question for Microsoft's MS-700 exam
Question #: 85
Topic #: 10
[All MS-700 Questions]

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your company has a Microsoft 365 subscription.

You need to prevent a user named User1 from permanently deleting private chats in Microsoft Teams.

Solution: You place the mailbox of User1 on Litigation Hold.

Does this meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: A

To restrict external Teams communication for both calling and personal chat to only organizational users that use the microsoft.com domain, you need to use the Teams admin center to configure the external access settings. Here are the steps to follow:

Sign in to the Teams admin center with your Microsoft 365 username and password.

In the left navigation, go to Org-wide settings > External access.

Under External access, turn on the toggle for Users can communicate with other Skype for Business and Teams users.

Under Cross-tenant access settings, click Manage settings.

In the Cross-tenant access settings pane, under Calling and chat, select Allow specific domains and then enter microsoft.com in the box below. This will allow your users to communicate with Microsoft users via calling and chat.

Click Save.

Note: You also need to make sure that microsoft.com has configured their external access settings to allow communication with your domain. See Communicate with users from other organizations for more details.


Contribute your Thoughts:

Allene
15 days ago
Ah, the good old 'Litigation Hold' trick. It's like using a sledgehammer to crack a nut, but hey, at least it gets the job done... sort of.
upvoted 0 times
...
Scarlet
15 days ago
Haha, placing someone's mailbox on Litigation Hold to prevent them from deleting private chats? That's like using a nuclear weapon to kill a fly. There must be a more targeted solution for this.
upvoted 0 times
...
Taryn
16 days ago
A) Yes, placing the mailbox on Litigation Hold will retain all data, including private chats, and meet the goal.
upvoted 0 times
...
Tiera
19 days ago
This solution doesn't seem right. Litigation Hold is more for preserving data for legal reasons, not for managing user permissions in Teams. I think there might be a better way to achieve the goal.
upvoted 0 times
...
Britt
19 days ago
B) No, placing the mailbox on Litigation Hold does not prevent User1 from deleting private chats.
upvoted 0 times
...
Evangelina
20 days ago
A) Yes, that should meet the goal of preventing User1 from permanently deleting private chats.
upvoted 0 times
...
Glory
23 days ago
Placing User1's mailbox on Litigation Hold will prevent them from permanently deleting private chats in Teams, but it's not the right solution. Litigation Hold is for legal purposes, not for preventing accidental deletions.
upvoted 0 times
...
Kasandra
25 days ago
A) Yes, I agree with Elise. Placing the mailbox on Litigation Hold should prevent User1 from permanently deleting private chats.
upvoted 0 times
...
Anna
27 days ago
B) No, placing the mailbox on Litigation Hold does not prevent User1 from deleting private chats in Microsoft Teams.
upvoted 0 times
...
Elise
1 months ago
A) Yes, that should meet the goal of preventing User1 from permanently deleting private chats.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77