Core Solutions of Microsoft Lync Server 2013: 070-336 Exam Premium File as PDF & Test Engine

Correct Answer:

Explanation:
http://technet.microsoft.com/en-us/library/jj204672.aspx

Client Interoperability in Lync 2013
This topic discusses the ability of Microsoft Lync Server 2013 clients to coexist and interact with clients from earlier versions of Lync Server and Office Communications Server.Server and Client Compatibility.
The following table shows the supported combinations of client versions and server versions. This table indicates whether sign-in is supported when the client attempts to connect to the server indicated. Lync Server 2013 supports the previous client version. Also, unlike previous releases, Lync Server 2010 supports the new Lync 2013 clients. This allows organizations who are upgrading from Lync Server 2010 to roll out new clients independent of Lync Server upgrades.


Interoperability among Clients
With the Lync Server 2013 release, various client versions can interact seamlessly in both peer-to-peer and conferencing scenarios. This section discusses feature availability when users interact with other users who are using different versions of clients and servers. Peer-to-Peer Feature Support
Peer-to-peer features are supported for users who are homed on different versions of the server and who are using different client versions. The end-user experience and available features are consistent with the capabilities of the user's client and the version of the server the user is signed in to. In other words:
If a user is signed in to Lync Server 2013 with an older client, the user will have the same experience he or she is used to. None of the new features introduced in Lync Server 2013 will be available until the user's client is upgraded.
If a user is signed in to Lync Server 2010 with a Lync 2013 client, any new features not supported by Lync Server 2010 will be unavailable until the user is moved to Lync Server 2013.
The following table compares feature availability in peer-to-peer sessions where the client is signed in to either Lync Server 2013 or Lync Server 2010.
Note:
Lync Web App and Lync 2010 Attendee are meeting-only clients and aren't included in this table.

Conferencing Feature Support
In Lync Server 2013 meetings, conferencing features are supported for users who are homed on different
versions of the server and who are using different clients and client versions. When clients join a Lync Server 2013 meeting, users have access to the features and capabilities shown in this table.

1.In Office Communicator 2007 R2, only desktop sharing (and not program sharing) is available.
2.Lync Server 2013 uses an updated mechanism for uploading PowerPoint files. Lync Web App users who join a meeting that was originally scheduled on Lync Server 2010 can view and navigate PowerPoint presentations, but cannot upload PowerPoint files.
3.If the meeting was scheduled on Lync Server 2013 and PowerPoint slides were uploaded by a Lync 2013 client, Lync 2010 users have view-only access to the slides. Conversely, if the PowerPoint slides were uploaded by a Lync 2010 user, Lync Server 2013 users will be able to view and slides and, if Office Web Apps Server is configured, access new capabilities such as higher resolution display, animations, slide transitions, and embedded video. For more information, see Configuring Integration with Office Web Apps Server and Lync Server 2013.
4.The presence and IM features in Office Communicator 2007 R2 are compatible with Lync Server 2013, but conferencing features are not. During migration from Office Communications Server 2007 R2, Office Communicator 2007 R2 is suitable for presence and IM interoperability, but users should use Lync Web App 2013 to join Lync Server 2013 meetings.
Scheduling Add-in Support
Server support for the various scheduling add-ins is consistent with server and client version compatibility. In general, the following scheduling add-ins are supported on Lync Server 2013. However, previous versions of add-ins do not provide new Lync 2013 add-in features, such as the option to mute all attendee audio and video upon meeting entry.
Online Meeting Add-in for Lync 2013 Provides the same features as the Online Meeting Add-in for Lync 2010, with the addition of attendee mute controls, which allow meeting organizers to schedule conferences that have attendee audio and video muted by default. Administrators can also customize the organization's meeting invitations by adding a custom logo, a support URL, a legal disclaimer URL, or custom footer text.
Online Meeting Add-in for Lync 2010 Provides scheduling for Lync meetings and removes the capability to schedule Office Live Meeting conferences.
Office Communicator 2007 R2 Conferencing Add-in Provides scheduling for both Office Live Meeting conferences and Office Communicator 2007 R2 conferences.
Note:
Live Meeting conferences cannot be scheduled on Lync Server 2013.

Support for Joining Meetings
All of the clients that Lync Server 2013 supports are allowed to join Lync 2013 meetings. Because Lync Web App is a web component of the server, in cases where Lync Web App is used to join a Lync Server 2013 meeting, the newer version of Lync Web App is always used.
Lync 2013 clients can join meetings hosted on Lync 2010 and Office Communications Server 2007 R2 with scaled-down functionality. In-meeting features are limited by the version of the server on which the meeting is hosted.

Correct Answer:

Explanation/Reference:
http://technet.microsoft.com/en-us/library/jj204800.aspx http://technet.microsoft.com/en-us/library/jj204756.aspx

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.


Topic 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.
Topic 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.

Correct Answer: C  🗳️

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

Correct Answer:

Explanation:
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.