Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. MS-102

Free Microsoft MS-102 Exam Questions (page: 16)

Page 16 of 85
PDF with 428 Questions
View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have a Microsoft 365 E5 subscription.
You need to use Microsoft Graph PowerShell to assign a Microsoft 365 E5 license to a new user named user1@contoso.com.
How should you complete the command? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Get-MgSubscribedSku
To assign a Microsoft 365 E5 license using Microsoft Graph PowerShell, you'll primarily use the Set- MgUserLicense cmdlet. This cmdlet allows you to assign or remove licenses from a user account.
Here's a breakdown of the process:
Find the E5 SKU ID:
Use Get-MgSubscribedSku to retrieve all your tenant's licensed SKUs.
Filter the results to identify the SKU with the SkuPartNumber equal to "SPE_E5" (or its current equivalent). This will provide you with the SkuId needed in the next step.
Box 2: Set-MgUserLicense
2. Assign the License:
Use Set-MgUserLicense to assign the E5 license to the target user. Specify the user's UPN using the -UserId parameter.
Use the -AddLicenses parameter to specify the E5 SKU ID (obtained in step 1) in a hash table format. You can optionally use -RemoveLicenses to remove any unwanted licenses simultaneously.
Code:
# Find the E5 SKU
$e5Sku = Get-MgSubscribedSku -All | Where SkuPartNumber -eq 'SPE_E5'
# Assign the E5 license to a user (replace with the user's UPN)
Set-MgUserLicense -UserId "user@example.com" -AddLicenses @{SkuId = $e5Sku.SkuId} -RemoveLicenses @()


Reference:

https://learn.microsoft.com/en-us/microsoft-365/enterprise/assign-licenses-to-user-accounts-with-microsoft- 365-powershell



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains a server named Server1 that runs Windows Server. The domain contains the users shown in the following table.


You have a Microsoft 365 subscription that contains the following user accounts: user1@contoso.com
user2@contoso.com
On Server1, you configure Microsoft Entra Connect Sync in staging mode and select the following organizational units (OUs):
OU=Department1,DC=Contoso,DC=LOCAL OU=Team1,OU=Department2,DC=Contoso,DC=LOCAL
You disable staging mode on Server1.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Yes
Yes - User1 syncs with user1@contoso.com.
User1 is in OU Department1.
Department1 was selected for Microsoft Entra Connect Sync in staging mode. User1 is synched.
Note: In a domain staging mode, Microsoft Entra Connect is used to synchronize AD DS users to Microsoft Entra ID. This process involves first installing and configuring Microsoft Entra Connect on a server, then using it to mirror users from your on-premises Active Directory environment into Microsoft 365. Once the initial synchronization is complete, any changes made in AD DS will be automatically replicated to Microsoft 365.
Turn off Staging Mode:
Once you're satisfied with the synchronization, turn off staging mode to allow changes in Microsoft Entra ID to also sync back to AD DS.
Box 2: Yes
Yes - User2 syncs with user2@contoso.com.
User2 is in OU Team, OU Department2.
OU Team, OU Department2 was selected for Microsoft Entra Connect Sync in staging mode. User2 is synched.
Box 3: No
No - User3 is created as a new user in Microsoft 365
User3 does not exist in Microsoft 365. User3 is in OU Department2.
User3 will not be selected in staging mode.


Reference:

https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-staging-server



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have a Microsoft 365 E5 subscription that contains a user named Admin1. Your company deploys a new branch office named Branch1.
You need to provide Admin1 with the ability to manage Branch1. The solution must meet the following requirements:
Admin1 must only be able to manage users that have Office location set to Branch1.
Admin1 must be able to reset passwords, manage user licenses, and modify user attributes only for the users in Branch1.
What should you use to organize the Branch1 users, and which role should you assign to Admin1? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: An administrative unit Use
Admin1 must only be able to manage users that have Office location set to Branch1.
In Microsoft 365, administrative units can be used to set up administrators for a branch location. They allow for delegated administrative permissions, limiting access to specific resources within a defined scope. This means a branch administrator can manage users, groups, and devices within their specific location without needing global admin access.
Box 2: User Administrator Role
Admin1 must be able to reset passwords, manage user licenses, and modify user attributes only for the users in Branch1.
User admin
Assign the User admin role to users who need to do the following for all users:
Add users and groups
*-> Assign licenses
*-> Manage most users properties
Create and manage user views
*-> Update password expiration policies
• Manage service requests
Monitor service health
The user admin can also do the following actions for users who aren't admins and for users assigned the following roles: Directory reader, Guest inviter, Helpdesk admin, Message center reader, Reports reader:
• Manage usernames
Delete and restore users
*-> Reset passwords
• Force users to sign out
Update (FIDO) device keys
Incorrect:
Password Administrator
A Password Administrator does not manage licenses or modify user attributes. They are primarily responsible for managing password-related aspects of the organization's users. License management and broad user attribute modification are typically handled by Global Administrators or other specific administrative roles.
* Helpdesk admin
Assign the Helpdesk admin role to users who need to do the following:
• Reset passwords
• Force users to sign out
• Manage service requests
• Monitor service health


Reference:

https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/administrative-units https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/about-admin-roles



View Related Case Study

You have Microsoft 365 E5 subscription that contains the identities shown in the following table.


You create a shared mailbox named Shared1.
Which identities can you add to Shared1 as a member?

  1. User1 only
  2. User1 and Group1 only
  3. User1 and Group2 only
  4. User1 and Group3 only
  5. User1, Group2, and Group3 only

Answer(s): D

Explanation:

In Microsoft 365, the following types of identities can be added as members to a shared mailbox: users and mail-enabled security groups. These members can then access the shared mailbox and its contents, subject to the permissions granted to them.
Users:
Individual user accounts within your Microsoft 365 organization can be added as members to a shared mailbox. This allows them to access the shared mailbox's emails, calendars, and other features.
Mail-enabled security groups:
You can also add mail-enabled security groups as members of a shared mailbox. This allows you to manage permissions for a group of users collectively. When you add or remove members from the security group, their access to the shared mailbox is automatically updated.


Reference:

https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have a Microsoft 365 subscription that uses Microsoft 365 Multi-Geo. The subscription contains two
Microsoft SharePoint Online sites named Site1 and Site2 that are stored in different Multi-Geo regions. You plan to configure a Microsoft 365 Backup policy.
You need to add Site1 and Site2 to the policy and configure the longest retention period available. What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Upload a list of the sites in a CSV file. To add the sites
To add SharePoint Online sites from different Multi Geo locations to a Microsoft 365 Backup policy, you need to configure the backup policy to include the specific sites or use a CSV file to upload a list of sites across different geographies. Ensure your tenant is configured for Multi-Geo and that the desired locations are added as satellite geographies.
Box 2: 1 year
Set the retention period to
The maximum retention period for Microsoft 365 backups is one year. This applies to backups of OneDrive accounts and Exchange mailboxes when a user is removed from a backup policy or deleted from Microsoft Entra ID. For SharePoint sites, the backup retention is 52 weeks from the last restore point. Microsoft plans to introduce options for longer or shorter retention periods in the future.


Reference:

https://learn.microsoft.com/en-us/microsoft-365/enterprise/multi-geo-capabilities-in-onedrive-and-sharepoint- online-in-microsoft-365
https://learn.microsoft.com/en-us/microsoft-365/backup/backup-overview



Viewing page 16 of 85



Post your Comments and Discuss Microsoft MS-102 exam prep with other Community members:

MS-102 Exam Discussions & Posts