70-336最も有効な質問と解答で勉強

正解：

Explanation/Reference:
http://technet.microsoft.com/en-us/library/gg398094.aspx
Certificate MUST have the Pool Name as the Subject Name (SN) and SAN Name and the Server Name in the SAN.
Topic 4, Litware, Inc Case B
Overview
General Overview
Litware, Inc. is an international manufacturing company that has 10,000 users.
Physical Locations
Litware has two offices. The offices are located in New York and Denver.
The offices connect to each other by using a WAN link.
Each office connects directly to the Internet.
Existing Environment
Active Directory Infrastructure
The network contains an Active Directory forest named litware.com.
The forest contains a single domain.
All domain controllers run Windows Server 2008 R2.
Each office contains two domain controllers.
Each office is configured as an Active Directory site.
Lync Server 2010 Infrastructure
Litware has a Lync Server 2010 infrastructure in the New York office. The infrastructure contains servers and appliances. The servers and appliances are configured as shown in the following table.

All of the servers that have Lync Server 2010 deployed are monitored by using Microsoft
System Center Operations Manager.
All client computers have either Microsoft Lync 2010 or Microsoft Office Communicator 2007 R2 installed.
Administrators configure the following Lync Server 2010 features:
IM and presence for all sites
External user access for IM and conferencing
Conferencing for all sites
Response groups
Group Chat
Problem Statements
Litware identifies the following issues:
Users report that other users who are not listed on their contact list can see their
presence information. This also occurs when the users set their privacy mode to
allow only the users on their contact list to see their presence information.
The users report that when they connect to meetings remotely, they cannot use presenter controls.
Requirements
Business Goals
Litware plans to minimize hardware and software purchasing costs.
Planned Changes
Litware plans to upgrade to Lync Server 2013 during the next six months and plans to implement the following changes during the upgrade:
Migrate the current Front End pool to an Enterprise Edition Front End pool named
fepooll that will contain two servers named Lyncl3_01 and Lyncl3_02.
Migrate Group Chat to Persistent Chat.
Technical Requirements
Litware identifies the following technical requirements for the planned changes:
Users running previous client versions must be able to use chat features after the
server is migrated to Persistent Chat.
Users who have mobile devices must be able to receive notifications if the Lync
mobile application is inactive.
A client computer named Monitor01 must be used to monitor client connectivity by
using synthetic transactions.
All response groups must be migrated to Lync Server 2013.
External users must be able to expand distribution groups.
External users must be able to download meeting content.
The Lync 2013 Windows Store app must be supported.
High Availability Requirements
The new Lync Server 2013 infrastructure in the New York office must be available if a single server fails.

正解：

Explanation:

Detailed Description
When an administrator makes a change of some kind to Lync Server (for example, when an administrator
creates a new voice policy
or changes the Address Book Server configuration settings) that change is recorded in the Central
Management store.
In turn, the change must then be replicated to all the computers running Lync Server services or server
roles.
In order to replicate data, the Master Replicator (running on the Central Management Server) creates a
snapshot of the modified configuration data;
a copy of this snapshot is then sent to each computer running Lync Server services or server roles.
On those computers, a replication agent receives the snapshot and uploads the modified data;
the agent then sends the Master Replicator a message reporting the latest replication status.
The Get-CsManagementStoreReplicationStatus cmdlet enables you to verify the replication status for any (or all) of the Lync Server computers in your organization.
Who can run this cmdlet:
By default, members of the following groups are authorized to run the Get-
CsManagementStoreReplicationStatus cmdlet locally:
RTCUniversalUserAdmins,
RTCUniversalServerAdmins.
To return a list of all the Role-Based Access Control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC Roles you have created yourself), run the following command from the Windows PowerShell prompt:
Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Get-
CsManagementStoreReplicationStatus"}

正解：

正解：

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.

正解：

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.