In this chapter, we will review the mock exam from the previous chapter and provide the answers and explanations for each question.
Explanation: Grant-CsTeamsUpgradePolicy is used for Skype for Business Online users, while Set-CsTeamsUpgradePolicy is specifically for Skype for Business 2019 (on-premises) deployments. SfBWithTeamsCollab co-existence mode will allow users to continue using Skype for calls, meetings, and chats but will allow channel collaboration in Teams.
Reference: https://docs.microsoft.com/en-us/powershell/module/skype/grant-csteamsupgradepolicy?view=skype-ps and https://docs.microsoft.com/en-us/microsoftteams/migration-interop-guidance-for-teams-with-skype#detailed-mode-descriptions
Explanation: Based on the information given, we can assume that users from other organizations are able to join our meetings as the meeting settings currently allow anonymous participants. We do not have information about blocked domains, and even if there were, users from those domains could still join meetings as anonymous individuals (they just wouldn't be able to collaborate in our teams and channels).
Explanation: Bots don't need calling plan licenses, as you use the free Phone System – Virtual User license for each of them instead. So, we only need 1,000 calling plan licenses for our human users and 5 of the free virtual user licenses. Each virtual bot (5 total queues and attendants) as well as each human user (1,000) will need a unique number, so we need 1,005 phone numbers.
Reference: https://docs.microsoft.com/en-us/microsoftteams/plan-auto-attendant-call-queue and https://docs.microsoft.com/en-us/microsoftteams/setting-up-your-phone-system#step-2-buy-and-assign-phone-system-and-calling-plan-licenses
Explanation: You should go to the Teams admin center, and under Org-wide settings | Teams upgrade, choose the option to download the Teams app in the background for Skype for Business users and set it to On. This will achieve the goal if the coexistence setting for the user is set to Teams only.
Reference: https://docs.microsoft.com/en-us/microsoftteams/setting-your-coexistence-and-upgrade-settings
Explanation: Configuration profiles may only be used with IP phones, collaboration bars, and Teams displays.
Explanation: Call analytics can be used to troubleshoot poor call quality and grant the Teams communications support specialist role to those needing tier 1 support abilities (limited) and the Teams communications support engineer role to those needing tier 2 (full access) support abilities to per-user call analytics.
Reference: https://docs.microsoft.com/en-us/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality
Explanation: Call queues can ring any available user in the queue, or all users simultaneously depending on the configuration.
Reference: https://docs.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue
Explanation: Auto attendants can be configured to provide choices to callers and route calls based on callers' responses.
Reference: https://docs.microsoft.com/en-us/microsoftteams/create-a-phone-system-auto-attendant
Explanation: Channel meetings automatically invite all team members, and discussions and/or recordings are saved to the channel, making any shared resources or chats available to team members as well.
Reference: https://docs.microsoft.com/en-us/MicrosoftTeams/tutorial-meetings-in-teams?tutorial-step=2
Explanation: Chat and channel messaging features, such as GIF usage, can be limited via messaging policies.
Reference: https://docs.microsoft.com/en-us/microsoftteams/messaging-policies-in-teams
Explanation: You can find the Teams settings under Org-wide settings in the Teams admin center. There is a section for files in which you can enable or disable certain cloud storage providers, such as Dropbox.
Reference: https://docs.microsoft.com/en-us/microsoftteams/enable-features-office-365#files
Explanation: App setup policies determine which apps appear in users' left-side navigation menus and in what order. They can be assigned to specific users and groups.
Reference: https://docs.microsoft.com/en-us/MicrosoftTeams/teams-app-setup-policies
Explanation: A calling plan license and phone number will be required for each user in the voice pilot project.
Reference: https://docs.microsoft.com/en-us/microsoftteams/set-up-calling-plans#step-2-buy-and-assign-licenses
Explanation: Any user performing an access review, User1 in this case, needs an Azure Active Directory Premium P2 license. Access reviews allow users to review group membership regularly and can be done by members themselves (if licensed appropriately) or by designated individuals (group owners or static chosen individuals).
Reference: https://docs.microsoft.com/en-us/azure/active-directory/governance/access-reviews-overview
Explanation: App permission policies control which apps (Microsoft, third-party, or custom) users are able to install. As with other policy types, you can assign these to specific individuals and groups. If a custom policy isn't assigned to a user, the global (org-wide default) policy will apply to them.
Reference: https://docs.microsoft.com/en-us/microsoftteams/teams-app-permission-policies
Explanation: Teams communications support specialist is the most appropriate role for the user. The Teams communications support engineer role would grant the user advanced troubleshooting tools. The Teams device administrator role would allow the user to manage devices configured for use in Teams, and the Teams service administrator role grants access to all areas and features within the Teams admin center.
Reference: https://docs.microsoft.com/en-us/microsoftteams/using-admin-roles
Explanation: The Skype for Business with Teams collaboration mode will not provide the meeting scheduling option. You should set the coexistence mode to Skype for Business with Teams collaboration and meetings.
Reference: https://docs.microsoft.com/en-us/microsoftteams/setting-your-coexistence-and-upgrade-settings
Explanation: You need to create a new security group and add the required users. Then, you will use PowerShell to ensure that no one in your organization can create teams apart from members of this security group. Microsoft 365 groups, distribution groups, and dynamic distribution groups may not be used to configure these settings.
Explanation: Guest access settings control whether people outside of your organization can be invited into your teams and channels. They do not control the ability to communicate with external users. You should instead navigate to Org-wide settings | External access.
Reference: https://docs.microsoft.com/en-us/microsoftteams/manage-external-access
Explanation: 2 is the correct answer as Microsoft Teams retention policies must be created in a separate retention policy. All other Microsoft 365 workloads may coexist in a single policy, but Teams must be separate.
Reference: https://docs.microsoft.com/en-us/microsoftteams/retention-policies
Explanation: Global administrators are exempt from group naming policies, as are user administrators and partner support (tiers 1 and 2).
Explanation: An alert policy allows you to select an administrator who can be notified of the new team creation.
Reference: https://docs.microsoft.com/en-us/microsoft-365/compliance/alert-policies?view=o365-worldwide
Explanation: The reports reader will provide the required access.
Reference: https://docs.microsoft.com/en-us/microsoftteams/teams-activity-reports
Explanation: The global (org-wide default) meeting policy will apply to all Teams users by default until you explicitly assign specific users to another policy.
Reference: https://docs.microsoft.com/en-us/microsoftteams/meeting-policies-in-teams
Explanation: Teams can only be restored for a 30-day period after they have been deleted. This is known as a soft delete.
Reference: https://docs.microsoft.com/en-us/microsoftteams/archive-or-delete-a-team#restore-a-deleted-team
3.142.249.42