Microsoft 074-338 Value Pack (Frequently Bought Together)

You are a member of the CsAdministrator group that supports the Lync datacenter for your company. The datacenter consists of one pool that is running Microsoft Lync Server 2013. You deploy SQL Mirroring. The principal server fails and you are unable to perform a manual failover for more than an hour. Users are placed into resiliency mode. You need to ensure that failover occurs automatically and without administrator intervention. What should you do?

• A. Configure SQL Mirroring with a witness.
• B. Deploy a Survivable Branch Server (SBS).
• C. Deploy a Survivable Branch Appliance (SBA).
• D. Configure a backup registrar.

You support Microsoft Lync Server 2013 servers in your customer's company network. Lync is configured as a federated partner with several business partners. The partners use Lync deployed with hosting providers. Your Lync servers are configured as an open federation. Lync users inform you that they are unable to communicate with a partner domain named fabrikam.com. You contact the partner and discover that they have recently changed their proxy server name. You need to restore communication with the federated partner. Which two cmdlets should you run? (Each correct answer presents part of the solution. Choose two.)

• A. Remove-CsHostingProvider -Identity "Fabrikam.com"
• B. Set-CsHostingProvider -Identity "Fabrikam.com" -VerificationLevel "AlwaysUnverifiable"
• C. New-CsHostingProvider -Identity Fabrikam.com -ProxyFqdn "server1.fabrikam.com" -Enabled $True
• D. Get-CsProxyConfiguration -Filter "service:*" | Remove-CsProxyConfiguration

You support a Microsoft Lync Server 2013 environment that consists of one Enterprise pool on a Front End Server Internal and external users cannot join online meetings using the Lync 2013 Lync Web App. The same users are able to join online meetings by using the Lync 2013 client. You need to diagnose the cause of the meeting join issues. Which cmdlet should you run from the Lync Server Management Shell?

• A. Test-CsMcxConference
• B. Set-CsWebService, with the AllowAnonymousAccessToLWAConference parameter
• C. Test-CsUcwaConference
• D. Test-CsAsConference

You support a customer whose network environment includes Microsoft Lync Server 2013 Enterprise, with two Front End Servers and two Back End Servers. The Back End Servers are deployed in a high availability configuration. You create a Front End pool named pool.contoso.com and implement DNS load balancing for client access to the Lync servers. Your internal DNS records have the following configuration: _gc._tcp.contoso.com SRV priority 0, weight 100, port 3268 dc1.contoso.com_ldap._tcp.contos.com SRV priority 0, weight 100, port 389 dc1.contoso.com_kerberos._tcp.contos.com SRV priority 0, weight 100, port 88 dc1.contoso.com_sip._tls.contoso.com SRV priority 0, weight 0, port 5061, pool.contoso.com FrontEndServer1 A 192.168.1.10FrontEndServer2 A 192.168.1.11BackEndServer1 A 192.168.1.20BackEndServer2 A 192.168.1.21Pool01 A 192.168.1.10Pool01 A
192.168.1.11 Your Lync 2013 clients fail to sign in automatically. The trace log of failed sign-in attempt is as follows: INFO :: QueryDNSSrv -DNS Name[_sipinternaltls._tcp.contoso.com]ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDRERROR :: ResolveHostNameUsingGetAddrInfo getaddrinfo(pool.contoso.com) failed WARN :: ResolveHostName
-getaddrinfo failed for pool.contoso.com ERROR :: ResolveHostNameUsingDnsQuery - DnsQuery(pool.contoso.com) failed WARN :: ResolveHostName - DNS lookup failed for pool.contoso.com ERROR :: ResolveHostName - Name resolution for pool.contoso.com failedERROR :: ResolveHostSyncResolveHostName failed ERROR :: GetDnsResults - did not get any resultERROR :: QueryDNSSrvGetDnsResults query: _sipinternaltls._tcp.contoso.com failed ERROR :: DNS_RESOLUTION_WORKITEM::ProcessWorkItemResolveHostName failed You need to ensure that internal Lync 2013 clients can sign in automatically. You also need to ensure that internal traffic is load balanced across the two Front End Servers. What should you do?

• A. Create the following host records: PoolA192.168.1.10PoolA192.168.1.11
• B. Create the following service record: _sipinternal._tls.contoso.com SRVPriority 0, weight 0, port 5061, FrontEndServer1.contoso.com
• C. Create the following host records:PoolA192.168.1.20PoolA192.168.1.21
• D. Create the following service record: _sip._tls.contoso.com SRVPriority 0, weight 0, port 5061, pool01.contoso.com
• E. Create the following host records: SipA 192.168.1.20SipA 192.168.1.21

You deploy Microsoft Lync Server 2013 Enterprise Edition and create a pool named Lync2013pool.Contoso.local. You configure the Lync admin URL to be admin.contoso.local. The Front End and Back End roles are installed on servers named FE2013 and BE2013. Your DNS server hosts the following records:
You attempt to open the Lync Server Control Panel and you receive an error message. You need to be able to open the Lync Server Control Panel. Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.)

• A. Modify the following DNS A record: admin.contoso.local to point 192.163.10.10
• B. Create the following DNS SRV record: _sipinternal._tcp.contoso.local SRV priority 0, weight 0, port 5061 lync2013pool.contoso.local
• C. Create the following DNS A record: Meet.contoso.local A 192.168.10.10
• D. Create the following DNS A record: lync2013pool.contoso.local A 192.168.10.10
• E. Create the following DNS A record: lyncdiscoverinternal.contoso.iocal A 192.168.10.10