Online Access Free 070-336 Practice Test

Explanation:
Reference: Configuring DNS Records
http://technet.microsoft.com/en-us/library/bb870389%28v=office.12%29.aspx

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.

Explanation: ANSWERED BY DAPPADEE & AP4S
MIXED QUESTIONS [Q. 23] Sales Users in Site 1 = Archive Internal IM only Sales Users in Site 2 = Archive Internal IM only Research Users in Site 2 = Archive External and Internal IM Marketing Users in Site 1 = Archive External IM only

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

Explanation:
Reference: Creating and Managing Chat Rooms
http://office.microsoft.com/en-us/communicator-help/creating-and-managing-chat-roomsHA010333635.aspx

Set-CsPersistentChatRoom -Identity pcpool.contoso.com\Announcements Presenters=com"}
@{ Add="sip:[email protected]} -Type Auditorium -Members @{ Add -Presenters =com"}

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.