74-338 무료 덤프문제 온라인 액세스

DRAG DROP You support a customer who
is deploying Microsoft Lync
Server 2013. The customer has completed deployment of the following components:
-A Lync Standard Edition Server,
-A Lync Edge Server,
-A media gateway connected to a Tl trunk,
-Appropriate rules for reverse proxy, and
-An Office Web App server with Microsoft SharePoint 2012.
Neither federation nor external access is enabled.
The customer installs a number of Lync 2013 clients on pilot user computers that are located inside their network. No one is able to access the Lync server from outside the network.
The pilot users report the following issues:
-When they make calls to local numbers, the calls do not work. An announcement states that they must not dial 1 to make a local call.
-When they make calls to long distance numbers, the calls connect, but the other end user reports that the caller's number does not appear correctly.
-When they receive long distance calls from outside, the caller ID information displayed in Lync does not match the caller's contact information.
You need to ensure that users in the customer's network can successfully have calls with users outside the network. You open the Voice Routing tab on the Lync
Server Control Panel as shown in the exhibit. (Click the Exhibit button.)

Which area should you look in to investigate each issue? (To answer, drag the appropriate voice routing area to the correct issue investigation or investigations. Each voice routing area may be used once or not at all. You may need to drag the split bar between panes or scroll to view content.)

정답:

Explanation:

HOTSPOT Your customer supports a Microsoft Lync Server 2013 environment. Users are unable to add a federated user to an AV conference. The affected users can view the federated user's presence, and the internal users' External Access Policy is configured to allow communication with federated users. You attempt to initiate a Telnet session to TCP port 5062 from your Lync Server 2013 Front End Server to your Lync Server 2013 Edge Server's internal interface, but you receive an error message that includes "Could not open a connection to the host, on port 5062: Connect failed." You decide to work with the network team to ensure that the Lync Server 2013 environment has the appropriate connectivity to ensure media path negotiation and media flow between the front end server and the Edge server. You need to ensure that users are able to add federated users to an AV conference. Which network ports should you confirm are open on the Lync Server 2013 Front End Server and on the Lync Server 2013 Edge Server? To answer, select the appropriate server or servers for each port in the answer area.

정답:

Explanation:

*STUN/MSTURN/TCP/443 / Edge Server internal interface / Fallback path for A/V media transfer between internal and external users, Survivable Branch Appliance or Survivable Branch Server if UDP communication cannot be established, TCP is used for file transfer and desktop sharing
*STUN/MSTURN/UDP/3478 / Edge Server internal interface / Preferred path for A/V media transfer between internal and external users, Survivable Branch Appliance or Survivable Branch Server
*5061 Access/SIP(MTLS)/TCP/5061 For federated and public IM connectivity using SIP
*5062 SIP/MTLS/TCP/5062 Authentication of A/V users (A/V authentication service) from Front End Server or Front End pool IP address or any Survivable Branch Appliance or Survivable Branch Server using this Edge Server

You support a customer whose network environment includes Microsoft Lync Server 2013 Standard deployed with an Edge Server that is connected to the Internet. Your customer currently has Lync Online configured for Hybrid mode with Office 365. You need to help your customer enable the Office Web Apps Server for users who are using on- premise Lync. What should you do?

• A.Install a Microsoft Web Access Companion Server (WAC) server on premise and configure the Lync Topology.
• B.Configure Office 365 SharePoint Online URL in the Lync Topology.
• C.Install Microsoft Web Access Companion Server (WAC) server components on Lync Pool Server.
• D.Configure Office 365 Microsoft Web Access Companion Server (WAC) URL in the Lync Topology.

You are a member of the CsAdministrator group that supports a Microsoft Lync Server 2013 datacenter. The datacenter consists of one pool. You implement Enterprise Voice. You do not have Call Admission Control (CAC) enabled. A user reports that when she receives a call to her Private Branch Exchange (PBX) phone, she doesn't get notified in her Lync Client. Other users do not have this problem. You need to ensure that the user is notified by Lync when a call comes in. What should you do?

• A.Change the users' Telephony setting to Remote call control.
• B.Change the voice policy to disable Public Switched Telephone Network (PSTN) reroute.
• C.Change the users' Telephony setting to Enterprise Voice.
• D.Change the voice policy to enable Simultaneous Ring reroute.

DRAG DROP You deploy a Microsoft Lync Server 2013 Enterprise pool named Lync2013.contoso.local.
The pool is configured with
the Session Initiation Protocol (SIP) domain litware.com. The environment includes the following:
-a Front End Server named Lync2013FE1
-a Back End Server named Lync2013BE
-an Edge Server named Lync2013Edge that is a member of Edge pool Edgepool.contoso.local
Your Lync 2013 topology supports the following access, meeting, administration, and external web service URLs:
-https://Dialin.litware.com
-https://Meet.litware.com
-https://Admin.contoso.local
-https://external.litware.com
You want to support external Lync Web App clients.
You plan to publish Lync 2013 HTTP Web services through a reverse proxy. You need to issue a certificate to publish Lync 2013 Web services through a reverse proxy firewall. Which three steps should you perform in sequence? (To answer, move the appropriate three actions from the list of actions to the answer area and arrange them in the correct order.)

정답:

Explanation:
Box 1:

Box 2: Create a publishing rule on the reverse proxy firewall to forward requests to the Front End Server.
Box 3: Install the certificate on reverse proxy firewall.
Note:
*Incorrect: No mobile devices or autodiscovery needed in this scenario.
*(step 1) You need to install the root certification authority (CA) certificate on the server running Microsoft Forefront Threat Management Gateway 2010 for the CA
infrastructure that issued the server certificates to the internal servers running Microsoft Lync Server 2013. You also must install a public web server certificate on your reverse proxy server. This certificate's subject alternative names should contain the published external fully qualified domain names (FQDNs) of each pool that is home to users enabled for remote access, and the external FQDNs of all Directors or Director pools that will be used within that Edge infrastructure. The subject alternative name must also contain the meeting simple URL, the dial-in simple URL, and, if you are deploying mobile applications and plan to use automatic discovery, the external Autodiscover Service URL as shown in the following table. *(step 2) If your internal deployment consists of more than one Standard Edition server or Front End pool, you must configure
web publishing rules for each external web farm FQDN and you will either need a certificate and web listener for each, or you must obtain a certificate whose subject alternative name contains the names used by all of the pools, assign it to a web listener, and share it among multiple web publishing rules. *(step 3 ) You create a certificate request on the reverse proxy. You create a request on another computer, but you must export the signed certificate with the private key and import it onto the reverse proxy once you have received it from the public certification authority.
Reference:
Request and Configure a Certificate for Your Reverse HTTP Proxy