You have an Exchange Server 2007 organization.
You recently deployed a server that has Exchange Server 2013 installed.
The Exchange Server organization contains three servers. The servers are configured as shown in the following table.
Server2 contains a mailbox for a user named User1. You move the mailbox of User1 to Server3. After
the move, User1 fails to access his mailbox by using Outlook Web App. Users who have mailboxes on
Server1 and Server2 can access their mailboxes by using Outlook Web Access. You need to ensure
that User1 can access his mailbox from the Internet by using Outlook Web App at
https://mail.contoso.com. The solution must ensure that users who have mailboxes on Server1 and
Server2 can continue to use Outlook Web Access. Which three actions should you perform? (Each
correct answer presents part of the solution. Choose three.)
A.
Export the certificate on Server1 and import the certificate to Server 3.
B.
On all of the Exchange servers, install a new certificate that contains the mail.contoso.com and
legacy.contoso.com names.
C.
Redirect all of the traffic from the Internet for mail.contoso.com to Server3.
D.
On all of the Exchange servers, install a new certificate that contains the Server1.contoso.com,
server2.contoso.com, server3.contoso.com, and legacy.contoso.com names.
E.
Create a host (A) record named legacy.contoso.com that points to Server1.
BCE
C is wrong because the question requires that the solution must ensure that users who have mailboxes on Server1 and Server2 can continue to use Outlook Web Access.
Of course they can.
In a co-existing scenario, Exchange 2013 CAS is the Internet Facing CAS, while Exchange 2010 CAS hides behind.
It is Exchange 2013 CAS’s job to make sure for those users whose mailbox are not yet migrated from Exchange 2010 to Exchange 2013, that their OWA requests are directed from Exchange 2013 CAS to Exchange 2010 CAS correctly.
This is done by pointing mail.contoso.com to Exchange 2013 CAS while creating a recording an point legacy.contoso.com to Exchange 2010 CAS. Exchange 2013 CAS would be configured with basic authentication while Exchange 2010 CAS would be configured to use NTLM (formerly called Intergrated Windows) authentication.
From Outlook cilent’s point of view, it doesn’t need to know about legacy.contoso.com, it only knows about mail.contoso.com whether the user’s mailbox is migrated to Exchange 2013 or still remains on Exchange 2010.
It is up to Exchange 2013 CAS to forward the request to Exchange 2013 Mailbox if user is already migrated, or forward the request to Exchange 2010 CAS and let Exchange 2010 CAS then forward the request to Exchange 2010 Mailbox if the user’s mailbox is not yet migrated to Exchange 2010.
For those users whose mailbos are not yet migrated from Exchange 2010 to Exchange 2013 yet, even though their mailbox still reside on Exchange 2010, but their Outlook client should still NEVER connect directly to Exchange 2010 CAS. They should always rely on Exchange 2013 CAS to forward their requests correctly.
Sorry, I made typo here. Where I said Exchange 2010, I was meant to say Exchange 2007.
A low-numbered rank means that your website gets a lot
of visitors.