Free Microsoft 70-336 Exam Dumps Questions & Answers

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.  Move-CsManagementServer
• B.  Invoke-CsManagementServerFailover
• C.  Import-CsConfiguration
• D.  Invoke-CsPoolFailover

Contoso is evaluating the Implementation of Push Notifications for Mobile Devices. You need to identify which tasks must be performed to enable the Push Notifications.
Which three cmdlets should you identify?
(Each correct answer presents part of the solution. Choose three.)

• A.  New-CsHostingProvider
• B.  Set-CsPublicProvider
• C.  New-CsAllowedDomain
• D.  Enable-CsPublicProvider
• E.  Set-CsPushNotificationConfiguration

You are evaluating the implementation of the planned Monitoring Solution.
You need to recommend which tasks must be performed to meet the Monitoring Requirements.
Which cmdlet should you include in the recommendation?

• A.  Set-CsArchivingConfiguration
• B.  Set-CsHealthMonitoringConfiguration
• C.  Set-CsCDRConfiguration
• D.  Set-CsQoEConfiguration

You are troubleshooting the issue reported by the Toronto Users.
You verify that the Logging Level of the Centralized Logging Service is set to AlwaysOn.
You need to gather additional troubleshooting information immediately to resolve the issue.
Which five actions should you perform?
To answer, move the five appropriate actions from the list of actions to the answer area and arrange
them in the correct order.
Select and Place:

Correct Answer:

Explanation/Reference:
Topic 1, Contoso Ltd Case A
Overview
General Overview
Contoso, Ltd. is an electronics parts company located in North American.
The company has 4,400 employees.
Contoso recently bought a company named Litware, Inc. Litware has an office in New York.
Litware has a Lync Server 2010 infrastructure and has Microsoft Lync 2010 clients deployed to all of its
client computers.
Physical Locations
Contoso has a main office and a satellite office. The main office is located in Toronto. The
satellite office is located in Boston. The Toronto office has 4,200 users. The Boston office has 200 users.
All offices connect to each other by using a WAN link.
Only the Toronto office connects directly to the Internet.
Existing Environment
Active Directory Environment
Contoso has an Active Directory forest named contoso.com. The forest contains a single domain. All domain controllers run Windows Server 2008 R2.
Lync Server Environment
Contoso has a Lync Server 2013 infrastructure and a Microsoft Exchange Server 2013 organization. The Lync Server 2013 infrastructure contains an Enterprise Edition Front End pool named Pool1. The network contains five servers. The servers are configured as shown in the following table.

The Lync Server infrastructure currently uses the names shown in the following table.

All users can remotely access the Lync Server services from a client computer.
The users cannot access the Lync Server services from a mobile device.
Some of the users have Lync 2010 installed. Most of the users run Lync 2013.
Problems Statements
Contoso identifies the following business issues:
Users in the Boston office report that there are delays in the audio stream during
conferences and that the audio frequently drops. Users in the other offices do not report this issue.
Users cannot share Microsoft PowerPoint presentations during web conferences.
Users can share other documents.
All of the users in the Toronto office report that they receive the following error
message from Lync 2013: "Lync can't connect to Exchange.
You might experience Contact list issues".
Requirements
Planned Changes
Contoso plans to implement the following changes:
Implement the unified contact store.
Deploy the Office Web Apps component.
Add a second Front End Server named Lync2 in the Toronto office.
Access Lync Server services by using mobile devices from the internal network and from the Internet.
Implement direct federation with Litware and other business partners.
All federated domains will have to be defined explicitly.
Administrative Requirements
A support technician named Techl must be able to perform all of the tasks currently
performed by the members of the CSHelpDesk group.
Additionally, Techl must also be able to edit conferencing policies.
Web Conferencing Requirements
Contoso identifies the following requirements for web conferencing:
Users from Litware must be able to download the content of web conferences.
Users must be able to share PowerPoint presentations during web conferences.
Users from Litware must be able to record web conferences.
A URL that points to a disclaimer must be provided.
Mobility Requirements
Contoso plans to provide all users the ability to connect by using mobile devices. When users connect from a mobile device, they must download their server settings automatically.

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.