Which DNS record should you identify?

###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 DNS record must be implemented for the planned federation relationship.
Which DNS record should you identify?
To answer, select the appropriate configurations for the DNS record in the answer area.

Hot Area:

###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 DNS record must be implemented for the planned federation relationship.
Which DNS record should you identify?
To answer, select the appropriate configurations for the DNS record in the answer area.

Hot Area:

Answer:

Explanation:
Note:
Protocol/TCP or UDP/Port,Source (IP address), Destination (IP address), Comments *XMPP/TCP/5269
IP address or addresses of XMPP federated partners
Access Edge External Standard server-to-server communication port for XMPP. Allows communication to the Edge-deployed XMPP proxy from federated XMPP
partners
*XMPP/TCP/5269
Access Edge External IP address or addresses of XMPP federated partners Standard server-to-server communication port for XMPP. Allows communication from
the Edge-deployed XMPP proxy to federated XMPP partners

Extensible Messaging and Presence Protocol (XMPP) TCP PORT 5269
Planned Federation Relationship in Litware-Case A is XMPP Federation The Partner Company uses XMPP for IM
Answer is: Use Port TCP/5269 which is for XMPP Federation
Port Summary – Single Consolidated Edge with Public IP Addresses The Lync Server 2013, Edge Server functionality described in this scenario architecture is very
similar to what was implemented in Lync Server 2010. The most noticeable addition is the port 5269 over TCP entry for the extensible messaging and presence
protocol (XMPP). Lync Server 2013 optionally deploys an XMPP proxy on the Edge Server or Edge pool and the XMPP gateway server on the Front End Server or
Front End pool. Planning information for the reverse proxy and federation are found in Scenarios for Reverse Proxy and Planning for SIP, XMPP Federation and
Public Instant Messaging sections, respectively.
Port and Protocol Details
We recommend that you open only the ports required to support the functionality for which you are providing external access.
For remote access to work for any edge service, it is mandatory that SIP traffic is allowed to flow bidirectionally as shown in the Inbound/Outbound edge traffic
figure. Stated another way, the SIP messaging to and from the Access Edge service is involved in instant messaging (IM), presence, web conferencing, audio/video
(A/V) and federation.
Firewall Summary for Single Consolidated Edge with Public IP Addresses: External Interface

In addition to IPv4, the Edge Server now supports IPv6. For clarity, only IPv4 is used in the scenarios.



Leave a Reply 0

Your email address will not be published. Required fields are marked *