MS-721 Question #159: Real Exam Question with Answer & Explanation

Question

Case Study 3 - Contoso, Ltd Overview Company Information Contoso, Ltd. is an international manufacturing company that has 2,000 employees. Contoso currently uses a third-party meeting service. The company plans to migrate the meeting service to Microsoft Teams and replace all legacy video teleconferencing (VTC) devices. Physical Locations Contoso has offices in Toronto, New York, Rome, and London. The company has a global sales team that works remotely. Existing Environment Active Directory Environment The on-premises network contains an Active Directory Domain Services (AD DS) forest named contoso.com. Microsoft 365 and Teams Environment Contoso has a Microsoft 365 subscription. All users are licensed for Microsoft 365 E5 and Teams Premium. All users are enabled for Teams Phone by using Operator Connect. The contoso.com domain syncs to Microsoft 365 by using Azure AD Connect cloud sync. All users use the Microsoft Authenticator app for multi-factor authentication (MFA) to cloud services. A Microsoft Surface Hub device is deployed to the boardroom in each office. The reception area at the Toronto office is configured to use a phone number of +14165555555 in Teams. Problem Statements Contoso identifies the following issues: - A user in the London office cannot locate the recorded files from a recurring Teams meeting. - Executives in the New York office report having to use Microsoft Authenticator to access their Microsoft OneDrive files from the Surface Hub. - A user in the Toronto office reports receiving incoming calls while attending Teams meetings instead of having calls sent automatically to voicemail. Requirements Planned Changes Contoso plans to implement the following changes: - Deploy a new Teams-certified endpoint to all the boardrooms and huddle spaces in all the offices. - Start a pilot project to deploy an Intelligent Speaker to the boardroom in the Rome office and evaluate transcription and voice attribution capabilities. - Deploy a Teams shared device to the lunchroom in the Toronto office. Calls placed to +14165555555 must ring in both the reception area and the lunchroom. Technical Requirements Contoso identifies the following technical requirements: - The endpoint deployed to each boardroom must include a console on the table. The endpoint must automatically invite the existing Surface Hub when joining a Teams meeting. - The sales team must be able to temporarily sign in to the endpoints deployed to the huddle spaces to respond to Teams messages and attend video calls. - The endpoints deployed to the huddle spaces must allow only outbound emergency calls when a user is NOT signed in. - During Teams meetings, the sales team must have a watermark displayed on shared content. You need to implement the planned changes for the lunchroom device in the Toronto office. What should you use?

Options

• Aa calling policy
• Bhot desking
• Ccall hold

Explanation

{"question_number": 7, "correct_answers": ["A"], "explanation": "Based on the Contoso case study context (Teams Phone deployment with 2,000 users, Microsoft 365 E5 and Teams Premium licensing), the answer is a calling policy (A). Calling policies in Microsoft Teams control user-level telephony features such as the ability to make private calls, use call forwarding, enable delegation, allow or prevent calls to PSTN numbers, and configure other calling behaviors. For a company migrating from a legacy PBX and deploying Teams Phone, calling policies are the primary tool for managing which calling features are available to which users. The other options - hot desking (B) and call hold (C) - are device or session-level features, not policy objects created in the Teams admin center to govern calling behavior.", "generated_by": "claude-sonnet", "llm_judge_score": 3}

No community discussion yet for this question.