You have a Lync Server 2013 Infrastructure.
The Infrastructure contains two Sites.
The Sites are located in New York and Rome.
Each Site has Enterprise Voice deployed and separate Dial Plans and Voice Policies.
You plan to deploy Dial-In Conferencing to both Sites.
In each Site, you create a Dedicated Conferencing Policy.
You assign the Conferencing Policies to the respective Users in each Site.
You create a Dial-In Conferencing Access Number.
When you attempt to assign a Region to the Number, you discover that the Regions are unavailable.
You need to ensure that you can add a Region to the Dial-In Conferencing Access Number.
What should you modify?

• A. The Meeting Configuration Settings
• B. Conferencing Policies
• C. The Voice Policies
• D. The Dial Plans

Explanation: Only visible for DumpsFree members. You can sign-up / login (it's free).

You have a Lync Server 2013 Infrastructure.
You need to configure Lync Server 2013 to meet the following conferencing requirements:
Ensure that a Legal Disclaimer is added to all Meeting Invitations.
Ensure that only Microsoft Lync 2013 Clients can be used to join conferences.
Ensure that Meeting Organizers manually Admit Remote Meeting Attendees who are users in
your Company.
Which cmdlets should you run?
To answer, drag the appropriate cmdlet to the correct requirement in the answer area.
Each cmdlet may be used once, more than once, or not at all.
Additionally, you may need to drag the split bar between panes or scroll to view content.
Select and Place:

You have a Lync Server 2013 Infrastructure that contains four Front End Pools. The Pools are configured as shown in the following table.

You configure Three Archiving Policies as shown in the following table

You need to identify which Archiving Setting will apply to each Group of Users.
Which archiving settings should you identify? Select and Place:

Explanation: ANSWERED BY DAPPADEE & AP4S
MIXED QUESTIONS [Q. 23] Sales Users in Site 1 = Archive Internal IM only Sales Users in Site 2 = Archive Internal IM only Research Users in Site 2 = Archive External and Internal IM Marketing Users in Site 1 = Archive External IM only

You need to identify the minimum number of required Public IP Addresses for each Lync Server 2013
component.
The solution must meet the Business Goals and Technical Requirements.
How many Public IP Addresses should you identify for each component?
To answer, select appropriate number of Public IP Addresses for each component in the answer area.
Exhibit:

Hot Area:

Explanation:
From Contoso Case Study B Case:
Technical Requirements
Contoso identifies the following technical requirements for the planned deployment:
Only Federation to Proseware must be allowed.
All of the Edge services must use default ports.
WAN traffic and Internet traffic must be minimized.
All of the user contacts stored in Lync Server 2013 must be backed up.
The sales department must have a dedicated dial-in conferencing number.
All other users in both the United States and Europe must use a pool of regional dialin conferencing numbers.
If a Single Component fails, all Lync Services MUST remain available without the need for manual intervention.
Performance degradation is acceptable during a component failure state.
The conversations of all the sales department users must be archived for 30 days.
The conversations of all the research department users must be archived for 90
days. No other conversations must be archived.
After the migration to Lync Server 2013, all client computers will have three
months to upgrade to Lync 2013. After three months, legacy clients must be
blocked from accessing the Lync Server 2013 infrastructure.
DUMP ANSWERS:
Edge Server: 3 Hardware Load Balancer:1 Web Component:1 Office Web Apps Server: 0
Topic 5, Contoso Ltd. Case B
Overview
General Overview
Contoso, Ltd. is an international manufacturing company that has 30,000 users.
Contoso has the following departments: sales, research, marketing, human resources,
executive, manufacturing, and legal. The sales department has 2,000 users.
All of the users in the sales department are located in the United States.
The research department has 3,000 users.
All of the users in the research department are located in Europe.
Physical Locations
Contoso has two main offices. The offices are located in Houston and Frankfurt.
Each office has 15,000 users.
The offices connect to each other by using an MPLS network. Each office connects directly to the Internet.
Existing Environment
Lync Server Infrastructure
Contoso has a Lync Server 2010 infrastructure that only uses internal instant messaging (IM) and
presence,
The infrastructure contains a single Enterprise Edition Front End pool that services all of the users.
Contoso uses a SIP domain of contoso.com for all of the users.
Client computers have either Microsoft Office Communicator 2007 R2 installed or Microsoft Lync 2010
installed.
Before deploying Lync Server 2013 and migrating the users to Lync Server 2013, you
implement a small pilot project to test the functionality of Lync Server 2013.
Problem Statements
The users in the pilot report that occasionally, they cannot sign in to Lync 2013.
Requirements
Business Goals
Contoso plans to upgrade to Lync Server 2013 during the next six months. Contoso must deploy all of the Lync Server conferencing and edge services. Contoso must also configure federation with its parent company, which is named Proseware, Inc. Proseware is located in Europe and has an Office Communication Server 2007 R2 infrastructure. Contoso must minimize hardware and software purchasing costs, while guaranteeing performance levels for all Lync Server 2013 workloads.
Planned Changes
Contoso plans to implement the following workloads in the Lync Server 2013 deployment:
Federation
Dial-in conferencing
External user access
Audio, video, and web conferencing
The ability to host Lync meetings that have external participants
The FQDNs of the edge services will be configured as shown in the following table.

Technical Requirements
Contoso identifies the following technical requirements for the planned deployment:
Only Federation to Proseware must be allowed.
All of the Edge services must use default ports.
WAN traffic and Internet traffic must be minimized.
All of the user contacts stored in Lync Server 2013 must be backed up.
The sales department must have a dedicated dial-in conferencing number.
All other users in both the United States and Europe must use a pool of regional dialin conferencing numbers.
If a Single Component fails, all Lync Services MUST remain available without the
need for manual intervention. Performance degradation is acceptable during a
component failure state.
The conversations of all the sales department users must be archived for 30 days.
The conversations of all the research department users must be archived for 90
days. No other conversations must be archived.
After the migration to Lync Server 2013, all client computers will have three
months to upgrade to Lync 2013. After three months, legacy clients must be
blocked from accessing the Lync Server 2013 infrastructure.
Security Requirements
Contoso identifies the following security requirements for the planned deployment:
All Lync Server conferences must use a unique URL.
Each Internet-facing service must have one or more dedicated public IP addresses.
Only the users in the human resources department must be prevented from
connecting to Lync Server remotely.

You have a Lync Server 2013 Infrastructure.
You create a new Common Area Phone.
You need to configure the Common Area Phone for Hot Desking.
The solution must enable Hot Desking for the Common Area Phone only.
What should you do?

• A. Modify the Global Voice Policy.
• B. Create a Per-User Client Policy and assign the Policy to a Phone Object.
• C. Modify the Global Client Policy.
• D. Create a Per-User Voice Policy and assign the Policy to a Phone Object.

Explanation: Only visible for DumpsFree members. You can sign-up / login (it's free).