Online Access Free 070-336 Practice Test

You have a Lync Server 2010 Infrastructure.
You plan to migrate to Lync Server 2013.
You have four Client Computers.
The Client Computers are configured as shown in the following table.

You need to identify which Client Computer types can use Audio Conferencing Hosted on Lync Server 2013 without installing any additional Software on the Client Computers.
Which client computer types should you identify?
To answer, select the appropriate Client Operating System and Installed Client Component in the answer area.
Hot Area:

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.

You have a Lync Server 2013 Infrastructure. The Infrastructure contains two Servers.
The Servers are configured as shown in the following table.

Pool Pairing is configured between Lyncfe01 and Lyncfe02.
Currently, the Central Management Store is hosted on Lyncfe01.
A hardware failure occurs on Lynfe01.
You manually perform a failover of all the User Services and the Central Management Store to Lyncfe02.
You resolve the hardware issue on Lyncfe01.
You need to restore all of the User Services and the Central Management Store to Lyncfe01.
Which three commands should you run?
(Each correct answer presents part of the solution. Choose three.)

• A.Invoke-CsPoolFailback -PoolFQDN Iyncfe01.contoso.com
• B.Invoke-CsManagementServerFailover -BackupSqIServerFQDN Iyncfe01.contoso.com BackupSqllnstanceName RTC -Force
• C.Invoke-CsPoolFailback -PoolFQDN Iyncfe02.contoso.com
• D.Install CSDatabase -CentralManagementDatabase -SqIServerFqdn Lyncfe01.contoso.com -SQLInstanceName RTC -Clean
• E.Move-CsManagementServer

You plan to deploy a Lync Server 2013 Edge Server Infrastructure.
The Edge Server deployment will be configured as shown in the following table.

You need to configure the DNS Records for Server1 to support the following features:
Automatic Client Sign-In
Discovery of Federated Partners
Which DNS Records should you configure?
To answer, configure the correct Service, Protocol, and Host for each SRV Record in the answer area.
Hot Area:

Correct Answer:

Explanation:
Reference: DNS Summary - Single Consolidated Edge with Private IP Addresses Using NAT
http://technet.microsoft.com/en-us/library/gg412787.aspx
DNS Summary -Single Consolidated Edge with Private IP Addresses Using NAT
DNS record requirements for remote access to Lync Server 2013 are fairly straightforward compared to those for certificates and ports. Also, many records are optional, depending on how you configure clients running Lync 2013 and whether you enable federation.
For details about Lync 2013 DNS requirements, see Determine DNS Requirements.
For details about automatic configuration of clients running Lync 2013 if split-brain DNS is not configured, see "Automatic Configuration without Split-Brain DNS" in Determine DNS Requirements.
The following table contains a summary of the DNS records that are required to support the single consolidated edge topology shown in the Single Consolidated Edge Topology figure. Note that certain DNS records are required only for automatic configuration of Lync 2013 and Lync 2010 clients. If you plan to use group policy objects (GPOs) to configure Lync clients, the associated automatic configuration records are not necessary. IMPORTANT: Edge Server Network Adapter Requirements
To avoid routing issues, verify that there are at least two network adapters in your Edge Servers and that the default gateway is set only on the network adapter associated with the external interface. For example, as shown in the Single Consolidated Edge Topology figure in Single Consolidated Edge with Private IP Addresses and NAT, the default gateway would point to the external firewall (10.45.16.1).
You can configure two network adapters in your Edge Server as follows: Network adapter 1 (Internal Interface)
Internal interface with 172.25.33.10 assigned.
No default gateway is defined.
Ensure that there is a route from the network containing the Edge internal interface to any networks that contain servers running Lync Server 2013 or Lync Server 2013 clients (for example, from 172.25.33.0 to 192.168.10.0).
Network adapter 2 (External Interface)
Three private IP addresses are assigned to this network adapter, for example 10.45.16.10 for Access Edge, 10.45.16.20 for Web Conferencing Edge, 10.45.16.30 for AV Edge
Note:
It is possible, though not recommended, to use a single IP address for all three Edge service interfaces. Though this does save IP addresses, it requires different port numbers for each service. The default port number is 443/TCP, which ensures that most remote firewalls will allow the traffic. Changing the port values to (for example) 5061/TCP for the Access Edge, 444/ TCP for the Web Conferencing Edge and 443/TCP for the AV Edge might cause problems for remote users where a firewall that they are behind does not allow the traffic over 5061/TCP and 444/TCP. Additionally, three distinct IP addresses makes troubleshooting easier due to being able to filter on IP address.
Access Edge IP address is primary with default gateway set to integrated router (10.45.16.1).
Web conferencing and A/V Edge IP addresses secondary.
Tip:
Configuring the Edge Server with two network adapters is one of two options. The other option is to use one network adapter for the internal side and three network adapters for the external side of the Edge Server. The main benefit of this option is a distinct network adapter per Edge Server service, and potentially more concise data collection when troubleshooting is necessary DNS Records Required for Single Consolidated Edge with Private IP Addresses Using NAT (Example)

You are evaluating a Disaster Recovery Solution for the planned Front End Pools.
You need to recommend a solution for restoring access to the
Central Management Store if the Front End Pool fails.
Which cmdlet should you include in the recommendation?

• A.Invoke-CsManagementServerFailover
• B.Invoke-CsPoolFailover
• C.Import-CsConfiguration
• D.Move-CsManagementServer

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:

Correct Answer:

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.