###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to identify the cause of the authentication issue for the pilot users.
Which four actions should you perform in sequence?
(To answer, move the appropriate four actions from the list of actions to the answer area and arrange them in the correct order.)
Select and Place:

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

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
the technical requirements.
How many public IP addresses should you identify for each component? (To answer, select the appropriate number of public IP addresses for each component in
the answer area.)
Select four.

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to recommend an archiving solution that meets the business goals and the technical requirements.
Which two actions should you recommend? (Each correct answer presents part of the solution.
Choose two.)

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to identify the minimum number of Lync Server 2013 servers and supporting server roles required in each Lync site to meet the business goals and the
technical requirements.

How many servers should you identify? (To answer, select the appropriate number servers in the answer area.)

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to identify the dial-in conferencing configurations required to meet the technical requirements for the sales department.
Which two configurations should you identify? (Each correct answer presents part of the solution. Choose two.)

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

The Lync Server 2013 infrastructure was implemented successfully three months ago.
You need to recommend a solution to meet the technical requirements.
Which cmdlet should you run?

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to ensure that the client computers that have Office Communicator 2007 R2 installed can use IM and presence and can join web conferences hosted on
Lync Server 2013. The solution must minimize administrative effort.
What should you do?

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to recommend a backup solution to meet the technical requirements. Which tool should you include in the recommendation?

###BeginCaseStudy###
Testlet 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
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 dial-in 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.

###EndCaseStudy###

You need to configure the Lync Server 2013 infrastructure to meet the security requirements for the human resources department. The solution must minimize
administrative effort.
What should you do?

###BeginCaseStudy###

Testlet 3
Litware, Inc Case A
Overview
General Overview
Litware, Inc., is an international manufacturing company that has 4,000 employees. The company has a sales department, a marketing department, a research
department, and a human resources department.
Litware has a partner company named Fabrikam, Inc. Fabrikam has an office in Paris. Fabrikam uses a XMPP-based instant messaging (IM) solution.
Physical Locations
Litware has seven offices located throughout North America and Europe. Litware has two data centers. The data centers are located in New York and London. All
communications for the North American offices are routed through the New York data center.
All communications for the European offices are routed through the London data center. The number of users in each office is shown in the following table.

Existing Environment
Active Directory Environment
Litware has an Active Directory forest named litwareinc.com. The forest contains a single domain. All domain controllers run Windows Server 2008 R2.
Each office contains five domain controllers. Each office is configured as an Active Directory site. Lync
Server Environment
Litware has a Lync Server 2010 infrastructure that contains two servers in the New York office. The servers are configured as shown in the following table.

The SIP domain is litwareinc.com.
Litware has a Microsoft Exchange Server 2013 organization.
Problem Statements
Users in the London office report poor video quality during conferences.
Requirements
Business Goals
Litware wants to minimize the costs associated with purchasing hardware and software.
Planned Changes
Litware plans to migrate the Lync Server 2010 infrastructure to Lync Server 2013. The migration will have a coexistence period of six months.
Litware plans to implement the following components as part of the planned migration:
Persistent Group Chat
The unified contact store
Enterprise Voice for all users
A central site in each data center
A branch site in each branch office
A Front End pool in each central site
Microsoft Lync Phone Edition devices
Pool pairing
Litware plans to create a federation relationship with Fabrikam.
Technical Requirements
Litware identifies the following technical requirements for the planned migration:
Users must be able to use all Lync Server features if a single server fails.
Users must be able to connect to the Lync Server infrastructure if a single central site fails.
Members of a group named Temp_Contractors must be prevented from using Microsoft Lync 2013 when they connect remotely.
Only users in the human resources department must be able to access and discover a persistent chat room named HRConfidential.
Security Requirements
Litware plans to deploy remote access. Some users work remotely from their customers’ offices, which have firewall restrictions.
All of the remote users must be able to connect to the Lync Server infrastructure by using TCP port 443.

###EndCaseStudy###

You need to identify which tasks must be performed to configure pool pairing between the Front End pools.
Which four actions should you identify?
To answer, move the four appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place: