You have a Lync Server 2013 infrastructure and a Microsoft Exchange Server 2010 organization. You have a SIP domain and an SMTP domain named contoso.com. You recently migrated the on-premise Exchange

Question

Options

• AFrom the Exchange Management Console, create an accepted domain.
• BFrom the Lync Server 2013 Control Panel, add a hosting provider named
• CIn the public DNS zone, create a service location (SRV) record
• DFrom the Lync Server 2013 Control Panel, add a hosting provider named exap.um.lync.com.
• EIn the public DNS zone, create a service location (SRV) record named _sip._tls.contoso.com.
• FFrom the Lync Server 2013 Control Panel, click the Enable Communications with Federated

• A
  78% (39)
• B
  2% (1)
• D
  12% (6)
• F
  8% (4)

Explanation

A: * An accepted domain is any SMTP namespace for which a cloud-based e-mail organization sends or receives e-mail. C, E: To get Office 365 Lync to work with your federated domain, you will need to add some DNS entries. These entries should normally be added to your external DNS. Granted it can also be added to your internal DNS zone if you are doing split brain DNS. To allow your federated domain users to automatically signon to Lync Online you will need 4 DNS records for each of the domains First you will need 2 SRV dns records created. _sip._tls.<domain> -> pointing to -> sipdir.online.lync.com _sipfederationtls._tcp.<domain> -> pointing to -> sipfed.online.lync.com Next you will need 2 CNAME records created. sip.<domain> -> pointing to -> sipdir.online.lync.com lyncdiscover.<domain> -> pointing to -> webdir.online.lync.com

No community discussion yet for this question.