仮想マシンがロードされるまでお待ちください。ロードしたら、ラボセクションに進むことができます。これには数分かかる場合があり、待機時間は全体のテスト時間から差し引かれません。
[次へ]ボタンが使用可能になったら、それをクリックしてラボセクションにアクセスします。このセクションでは、ライブ環境で一連のタスクを実行します。ほとんどの機能はライブ環境と同じように利用できますが、一部の機能(コピーと貼り付け、外部Webサイトへの移動機能など)は設計上不可能です。
スコアリングは、ラボで説明されているタスクを実行した結果に基づいています。言い換えれば、タスクをどのように達成するかは問題ではありません。それを正常に実行すると、そのタスクのクレジットを獲得できます。
ラボの時間は個別に設定されていません。この試験には、完了する必要のあるラボが複数ある場合があります。各ラボを完了するのに必要なだけの時間を使用できます。ただし、提供された時間内にラボおよび試験の他のすべてのセクションを完了できるように、時間を適切に管理する必要があります。
ラボ内で[次へ]ボタンをクリックして作業を送信すると、ラボに戻ることができないことに注意してください。

必要に応じて、次のログイン資格情報を使用します。
ユーザー名を入力するには、[サインイン]ボックスにカーソルを置き、下のユーザー名をクリックします。
パスワードを入力するには、[パスワードの入力]ボックスにカーソルを置き、下のパスワードをクリックします。
Microsoft 365ユーザー名:
[email protected]Microsoft 365パスワード:xxxxxx
Microsoft 365ポータルがブラウザーに正常に読み込まれない場合は、Ctrlキーを押しながらKキーを押して、新しいブラウザータブでポータルを再読み込みします。
以下の情報は、技術サポートのみを目的としています。
ラボインスタンス:XXXXXX
ユーザーがMicrosoftOutlookで電子メールメッセージを迷惑メールではないとマークしたときに、通知電子メールが
[email protected]に送信されるようにする必要があります。
このタスクを完了するには、Microsoft365管理センターにサインインします。
正解:
See explanation below.
Explanation
Go to the Microsoft 365 Defender portal and under select Policies & rules > Alert policy.
An alert policy consists of the following settings and conditions.
- Activity the alert is tracking. You create a policy to track an activity or in some cases a few related activities, such a sharing a file with an external user by sharing it, assigning access permissions, or creating an anonymous link. When a user performs the activity defined by the policy, an alert is triggered based on the alert threshold settings.
- Activity conditions. For most activities, you can define additional conditions that must be met to trigger an alert. Common conditions include IP addresses (so that an alert is triggered when the user performs the activity on a computer with a specific IP address or within an IP address range), whether an alert is triggered if a specific user or users perform that activity, and whether the activity is performed on a specific file name or URL. You can also configure a condition that triggers an alert when the activity is performed by any user in your organization. The available conditions are dependent on the selected activity.
You can also define user tags as a condition of an alert policy. This results in the alerts triggered by the policy to include the context of the impacted user. You can use system user tags or custom user tags.
- When the alert is triggered. You can configure a setting that defines how often an activity can occur before an alert is triggered. This allows you to set up a policy to generate an alert every time an activity matches the policy conditions, when a certain threshold is exceeded, or when the occurrence of the activity the alert is tracking becomes unusual for your organization.
If you select the setting based on unusual activity, Microsoft establishes a baseline value that defines the normal frequency for the selected activity. It takes up to seven days to establish this baseline, during which alerts won't be generated. After the baseline is established, an alert is triggered when the frequency of the activity tracked by the alert policy greatly exceeds the baseline value. For auditing-related activities (such as file and folder activities), you can establish a baseline based on a single user or based on all users in your organization; for malware-related activities, you can establish a baseline based on a single malware family, a single recipient, or all messages in your organization.
- Alert category. To help with tracking and managing the alerts generated by a policy, you can assign one of the following categories to a policy.
- Data loss prevention
- Information governance
- Mail flow
- Permissions
- Threat management
- Others
When an activity occurs that matches the conditions of the alert policy, the alert that's generated is tagged with the category defined in this setting. This allows you to track and manage alerts that have the same category setting on the page in the compliance center because you can sort and filter alerts based on category.
- Alert severity. Similar to the alert category, you assign a severity attribute (Low, Medium, High, or Informational) to alert policies. Like the alert category, when an activity occurs that matches the conditions of the alert policy, the alert that's generated is tagged with the same severity level that's set for the alert policy.
Again, this allows you to track and manage alerts that have the same severity setting on the Alerts page. For example, you can filter the list of alerts so that only alerts with a severity are displayed.
- Email notifications. You can set up the policy so that email notifications are sent (or not sent) to a list of users when an alert is triggered. You can also set a daily notification limit so that once the maximum number of notifications has been reached, no more notifications are sent for the alert during that day. In addition to email notifications, you or other administrators can view the alerts that are triggered by a policy on the Alerts page. Consider enabling email notifications for alert policies of a specific category or that have a higher severity setting.
Reference:
https://docs.microsoft.com/en-us/microsoft-365/compliance/alert-policies?view=o365-worldwide#how-alert-poli