Information Security Administrator Associate (SC-401) - Microsoft

<img src="https://examsqa.com/storage/question-images/information-security-administrator-associate-sc-401_page_4_Im6.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
The goal is to automatically label documents in Site1 that contain credit card numbers. To achieve this, we need a sensitivity label with an auto-labeling policy based on a sensitive info type that detects credit card numbers.<br />
<br />
Step 1: Create a Sensitive Info Type<br />
● A sensitive info type is needed to detect credit card numbers in documents. ● Microsoft Purview includes built-in sensitive info types for credit card numbers, but we can also create a custom one if necessary.<br />
<br />
Step 2: Create a Sensitivity Label<br />
● A sensitivity label is required to classify and protect documents containing sensitive information. ● This label can apply encryption, watermarking, or access controls to credit card data.<br />
<br />
Step 3: Create an Auto-Labeling Policy<br />
● An auto-labeling policy ensures that the sensitivity label is applied automatically when credit card numbers are detected in Site1. ● This policy is configured to scan files and automatically apply the correct sensitivity label.

To meet the requirement that all administrative users must be able to create Microsoft 365 sensitivity labels, we need to assign the Sensitivity Label Administrator role to the correct users. Sensitivity Label Administrator Role Responsibilities ● Create and manage sensitivity labels in Microsoft Purview.<br />
<br />
This role allows users to: ● Publish and configure auto-labeling policies. ● Modify label encryption and content marking settings.<br />
<br />
Review of Admin Roles from the Table:<br />
<br />
<img src="https://examsqa.com/storage/question-images/information-security-administrator-associate-sc-401_page_6_Im7.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Users that must be assigned the Sensitivity Label Administrator role: ● Admin2 (Compliance Data Administrator) ● Admin3 (Compliance Administrator) ● Admin1 (Global Reader) (should be assigned this role to fulfill the requirement that all admins can create labels).

<img src="https://examsqa.com/storage/question-images/information-security-administrator-associate-sc-401_page_7_Im9.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
To detect and protect confidential documents, we need a custom rule to identify project codes that start with 999 (since they are classified as confidential). Box 1: A Sensitive Info Type (SIT) allows Microsoft Purview DLP policies to recognize structured data (e.g., project codes). DLP policies require a sensitive info type to detect content based on patterns, keywords, or dictionary terms. A sensitivity label alone does not define detection logic—it is used for classification and protection after content is identified. Box 2: Since project codes follow a structured 10-digit pattern, we should use a Regular Expression (Regex) to match project codes that start with 999.<br />
<br />
Example Regex pattern:<br />
999\d{7}<br />
This pattern detects a 10-digit number starting with "999".

<img src="https://examsqa.com/storage/question-images/information-security-administrator-associate-sc-401_page_9_Im11.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Understanding DLP Policy Impact on File Access<br />
<br />
The DLP policy (DLPpolicy1) applies to Site2 and restricts access when: ● Content contains SWIFT Codes. ● Instance count is 2 or more. File Analysis (Based on SWIFT Codes Count)<br />
<br />
<img src="https://examsqa.com/storage/question-images/information-security-administrator-associate-sc-401_page_9_Im12.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Files that remain accessible (not restricted by DLP): ● File1.docx (Contains only 1 SWIFT Code → Below restriction threshold)<br />
<br />
User access after DLP policy is applied:<br />
<br />
<img src="https://examsqa.com/storage/question-images/information-security-administrator-associate-sc-401_page_10_Im13.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
User1 (Site Owner): ● Has higher privileges and can override DLP restrictions (through admin intervention). ● Can access 2 files (File1.docx + override access to another file).<br />
<br />
User2 (Site Visitor): ● Has read-only access but DLP blocks access to restricted files. ● Can only access 1 file (File1.docx), since all others are restricted.

Understanding Site4's Retention Policies: ● Site4RetentionPolicy1 deletes items older than 2 years from creation. If a file was created on January 1, 2021, it would be deleted after January 1, 2023. ● Site4RetentionPolicy2 retains files for 4 years from creation. If a file was created on January 1, 2021, it will be kept until January 1, 2025, but not deleted after that (policy states "Do nothing"). Statement 1 - Yes, because Site4RetentionPolicy2 ensures files are retained for 4 years. Statement 2 - Yes, because Site4RetentionPolicy2 retains the file for 4 years (until January 1, 2025). Statement 3 - No, because retention is only for 4 years (until January 1, 2025). After that, the policy does "nothing," meaning the file is no longer recoverable after that period.