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 SC-400 Topic 5 Question 102 Discussion

Actual exam question for Microsoft's SC-400 exam
Question #: 102
Topic #: 5
[All SC-400 Questions]

You have a Microsoft 365 tenant that uses the following sensitivity labels:

* Confidential

* Internal

* External

The labels are published by using a label policy named Policy1.

Users report that Microsoft Office for the wen apps do not display the Sensitivity button. The Sensitivity button appears in Microsoft 365 Apps that are installed locally.

You need to ensure that the users can apply sensitivity labels to content when they use Office for the web apps.

Solution: You run the Execute-AzureAdLabelSync cmdlet.

Does this meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: A

To retain all Microsoft Exchange items in Alex Wilber's mailbox that contain the word ''Falcon'' and were created in the year 2021, follow these steps:

Create a Retention Policy:

Sign in to theMicrosoft 365 compliance center.

Navigate toPoliciesand click onRetention.

Create a new retention policy (e.g., ''Falcon Retention 2021'').

Specify the retention period (e.g.,2 yearsfrom the creation date).

Set the condition to include items containing the word ''Falcon.''

Apply the Retention Policy to Alex Wilber's Mailbox:

Assign the retention policy to Alex Wilber's mailbox.

Ensure that the policy targets items created in the year 2021.

Validate the Policy:

Test the policy thoroughly to ensure it correctly retains the specified items.

Monitor the mailbox to verify that the retention actions are enforced.


Contribute your Thoughts:

Leanna
1 months ago
Haha, the question says 'Does this meet the goal?' - I think the real goal here is to keep us on our toes and make sure we're really thinking through the problem, not just going with the first solution that comes to mind. 'No' seems like the safer bet.
upvoted 0 times
Merilyn
9 days ago
Haha, the question says 'Does this meet the goal?' - I think the real goal here is to keep us on our toes and make sure we're really thinking through the problem, not just going with the first solution that comes to mind. 'No' seems like the safer bet.
upvoted 0 times
...
Lilli
10 days ago
B) No
upvoted 0 times
...
Dannie
23 days ago
A) Yes
upvoted 0 times
...
...
Alise
1 months ago
Well, at least the question is straightforward. Maybe the cmdlet is a red herring and the real solution is something more obvious, like checking the label policy or web app settings. I'm going to go with 'No' on this one.
upvoted 0 times
Kallie
1 days ago
I agree, I think there might be something else causing the issue. I'll also go with 'No'.
upvoted 0 times
...
Stanton
8 days ago
B) No
upvoted 0 times
...
Arlene
27 days ago
A) Yes
upvoted 0 times
...
...
Harley
2 months ago
Maybe we should try a different solution to ensure users can apply sensitivity labels.
upvoted 0 times
...
Dona
2 months ago
I agree with Nguyet, running that cmdlet won't solve the issue.
upvoted 0 times
...
Cordell
2 months ago
I agree, the question seems to imply that the issue is with the web apps specifically, so running a cmdlet might not be the right approach. Perhaps we need to look at the label policy configuration or other web app settings.
upvoted 0 times
Deonna
21 days ago
I think B) No might be a better option here.
upvoted 0 times
...
Gayla
26 days ago
A) Yes
upvoted 0 times
...
...
Nguyet
2 months ago
No, I don't think that will work.
upvoted 0 times
...
Tuyet
2 months ago
Hmm, I'm not sure the Execute-AzureAdLabelSync cmdlet is the right solution here. Wouldn't we need to adjust the label policy or label settings to ensure the Sensitivity button is visible in the Office web apps?
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