Microsoft MS-203 Practice Test - Questions Answers, Page 29

Reference:

https://docs.microsoft.com/en-us/exchange/hybrid-deployment/configure-hybrid-deployment-certificate

Explanation: When replacing a certificate used in a hybrid deployment, you should run the Hybrid

Configuration wizard again to update the certificate information in the hybrid configuration settings. This process updates the certificate used by the hybrid deployment and ensures that email delivery between the on-premises Exchange Server and the Exchange Online tenant is successful.

Set-Mailbox -Identity * -ArchiveQuota "Unlimited"

To ensure that the default size of each user's archive mailbox increases automatically when the mailbox approaches the storage limit and to apply the solution automatically to all current and future mailboxes, you can use the Set-Mailbox cmdlet in PowerShell and specify the –ArchiveQuota parameter.

Here is an example of how you could complete the PowerShell command:

Copy code

Set-Mailbox -Identity * -ArchiveQuota "Unlimited"

This command will set the archive mailbox size to unlimited for all mailboxes in the tenant.

Please note that, when you set the archive mailbox size to unlimited, the user's mailbox will continue to grow until it reaches the available storage space in the tenant.

You could also set a specific size limit, for example:

Copy code

Set-Mailbox -Identity * -ArchiveQuota "50 GB"

This command will set the archive mailbox size to 50 GB for all mailboxes in the tenant.

You can then use the Get-Mailbox cmdlet to verify the new archive mailbox size for all mailboxes in the tenant:

Copy code

Get-Mailbox -Identity * | Select DisplayName, ArchiveQuota

This command will return the DisplayName and ArchiveQuota properties for all mailboxes in the

tenant.

Reference: https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/audit-logsearch

Explanation: The Audit feature in the Microsoft 365 Defender portal allows you to track any modifications made to the policies in your tenant, including the Anti-malware Policy1. You can use the Audit feature to view the name of the user that modified the policy, the old and new values settings modified in Policy1 and how the modifications compare to the baseline settings of Standard Preset Security Policy.

You can use an eDiscovery case to create and manage eDiscovery holds that can be applied to user mailboxes and other content locations in Microsoft Purview1. You can also use an eDiscovery case to search for and export content from mailboxes and other locations1.

An eDiscovery case is different from a Litigation Hold, which is a hold that is applied to user mailboxes in Exchange Online1. A Litigation Hold isn’t identified by a GUID1. A sensitive info type is a predefined or custom entity that can be used to identify and protect sensitive data in Microsoft Purview2. It is not related to placing a hold on email messages. A data loss prevention (DLP) policy is a policy that helps prevent the accidental or intentional sharing of sensitive information outside your organization2. It is not related to placing a hold on email messages. An information barrier segment is a group of users who are allowed or blocked from communicating with each other in Microsoft Teams or SharePoint Online2. It is not related to placing a hold on email messages.

Preset security policies are policies that provide a centralized location for applying all of the recommended spam, malware, and phishing policies to users at once1. The policy settings are not configurable and are set by Microsoft based on best practices1.

There are two types of preset security policies: Standard protection and Strict protection1. Standard protection is a baseline protection profile that’s suitable for most users1. Strict protection is a more aggressive protection profile for selected users who are high value targets or priority users1.

If you want to apply Policy1 to the Executives group, you need to remove them from the Strict protection preset security policy first. Otherwise, the preset security policy will take precedence over Policy1 and prevent it from being applied2. To remove the Executives group from the Strict protection preset security policy, you can follow these steps2:

Login to the Microsoft Security portal at https://security.microsoft.com.

On the left nav, under Email & collaboration, select Policies & rules.

Select Threat policies.

Select Preset Security Policies underneath the Templated policies heading

Select Manage underneath the Strict protection preset.

Select Specific recipients and remove the Executives group from the list of recipients.

Select Save.

Users in Dept1 should use S/MIME encryption1. S/MIME is a standard for public key encryption and signing of email messages1. It allows users to digitally sign and encrypt email messages as required using certificates1. S/MIME provides end-to-end encryption and ensures message integrity and sender authentication1. Email messages sent from Dept2 to an external email domain should use TLS encryption1. TLS is a protocol that encrypts the connection or session between two servers1. It protects email messages during transit only and does not require any action from the sender or recipient1. TLS provides opportunistic encryption and ensures message confidentiality and server authentication1. Email messages sent from Dept3 to an external email domain should use Microsoft Purview Message Encryption2. Microsoft Purview Message Encryption is an online service that encrypts email messages and attachments using rights management policies2. It allows users to send encrypted email messages to anyone inside or outside the organization using various email services2. Microsoft Purview Message Encryption provides persistent encryption and ensures message confidentiality and authorization policies2.

1. Create a connector1. A connector is a configuration setting that controls how email messages are delivered to or received from your own email servers or a partner organization1. You need to create a connector to route mail between Exchange Online and your on-premises alarm system that uses SMTP1. You can specify the IP address of your alarm system as a trusted sender and configure the connector to use certificate-based authentication or IP address-based authentication1.

2. Configure direct send2. Direct send is an option that allows you to send mail directly from your printer or application to Microsoft 365 or Office 365 without using a local email server2. You need to configure direct send on your alarm system settings to use an MX record of the tenant as the SMTP server address2. For example, contoso-com.mail.protection.outlook.com2. Direct send does not require TLS encryption or SMTP authentication2.

Box 1 = Compliance Administrator1 the role group that you should add User1 to is:

The Compliance Administrator role group grants permissions to manage compliance features in

Microsoft 365, such as content search, audit log search, eDiscovery cases, and data loss prevention policies1. Members of this role group can also search all mailboxes and purge email from all mailboxes using Security & Compliance PowerShell23. This role group uses the principle of least privilege by not granting permissions to manage other features or settings in Microsoft 3651.

Box 2 = Microsoft Purview compliance portal1. The Microsoft Purview compliance portal is a webbased portal that allows you to manage compliance features in Microsoft 365, such as content search, audit log search, eDiscovery cases, and data loss prevention policies1. You can use this portal to search all mailboxes and purge email from all mailboxes using Security & Compliance

PowerShell23. You need to have the appropriate permissions to perform these tasks2