Download Microsoft.MD-102.PassLeader.2024-09-03.42q.vcex

Re-provision the sales department computers by using Windows AutoPilot. Windows Autopilot Deployment for existing devices, install required modules: Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force Install-Module AzureAD -Force Install-Module WindowsAutopilotIntune -Force Install-Module Microsoft.Graph.Intune -Force Reference: https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/existing-devices   

Ensure that users can sign in to the Azure AD-joined computers by using a PIN. The PIN must expire every 30 days. Group Policy settings for Windows Hello for Business. These policy settings are available in User configuration and Computer Configuration under Policies > Administrative Templates > Windows Components > Windows Hello for Business. Reference: https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-manage-in-organization 

Ensure that the projects in Azure DevOps can be accessed from the corporate network only. Reference: https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/manage-conditional-access?view=azure-devops

The Los Angeles office has 500 developers. The developers work flexible hours ranging from 11 AM to 10 PM. 

From the scenario: Ensure that the company name and logo appears during the Out of Box Experience (OOBE) when using Windows AutoPilot. Company Branding: When you use Windows AutoPilot to deploy new devices, you want the process to be friendly and familiar for the users going through the process. One of the ways that is done is by customizing the logon experience to include logos and company-specific text. The basic steps: Sign into the Azure Portal as a tenant admin. Navigate to Azure Active Directory -> Company branding. Click Edit to configure the needed settings. Fill in all the customizations (Including the company logo and company name) Properties: you can set that value in the Name field of the Azure AD tenant properties: Reference: https://blogs.technet.microsoft.com/mniehaus/2017/12/22/windows-autopilot-azure-ad-branding/ 

Box 1: Employees in the research department must be prevented from copying patented information from trusted applications to untrusted applications. This requires an App protection policy. App protection policies make sure that the app-layer protections are in place. For example, you can: Require a PIN to open an app in a work context Control the sharing of data between apps Prevent the saving of company app data to a personal storage location  Box 2: Employees in the sales department must be prevented from forwarding email that contains bank account information. Azure Information Protection is a cloud-based solution that helps an organization to classify and optionally, protect its documents and emails by applying labels. Labels can be applied automatically by administrators who define rules and conditions, manually by users, or a combination where users are given recommendations.  Reference: https://docs.microsoft.com/en-us/intune/app-protection-policy https://docs.microsoft.com/en-us/azure/information-protection/what-is-information-protection 

Scenario: Technical requirements include: Block iOS devices from sending diagnostic and usage telemetry data. Intune includes device restriction policies that help administrators control Android, iOS, macOS, and Windows devices. These restrictions let you control a wide range of settings and features to protect your organization's resources. For example, administrators can: Allow or block the device camera Control access to Google Play, app stores, viewing documents, and gaming Block built-in apps, or create a list of apps that allowed or prohibited Allow or prevent backing up files to cloud and storage accounts Set a minimum password length, and block simple passwords  Reference: https://docs.microsoft.com/en-us/intune/device-restrictions-configure https://docs.microsoft.com/en-us/mem/intune/configuration/device-restrictions-ios#settings-apply-to-all-enrollment-types-4 

MDM and MAM are not under Azure portal anymore. You have to go to Endpoint > Devices > Enroll devices | Windows enrollment > Automatic Enrollment. https://docs.microsoft.com/en-us/sccm/comanage/tutorial-co-manage-clients 

Box 1: Device 3 only Policy1 applies to Device3 (Android)  Box 2: Device 4 only Policy2 applies to Device4 (iOS)  Reference: https://docs.microsoft.com/en-us/intune/device-profile-assign

Box 1: 10 devices User1 is a member of GroupA. GroupA device limit is 10.  Box 2: 15 devices User2 is a member of GroupB. GroupB device limit is 15.  https://docs.microsoft.com/en-us/mem/intune/enrollment/device-enrollment-manager-enroll#limitations-of-devices-that-are-enrolled-with-a-dem-account