DRAG DROP
You have an Exchange Server 2016 organization. The organization contains two Mailbox servers.
You have a database that is replicated to both servers. The database contains 500 mailboxes.
You add new volumes to the Mailbox servers.
You need to move all of the mailbox data to the new volumes. The solution must meet the following
requirements:
Ensure that multiple copies of the mailbox data are available at all times.
Minimize downtime for the mailbox users.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.
Select and Place:
Answer: 
Explanation:
Use the Move-DatabasePath cmdlet to set a new path to the location of a database on the specified Mailbox
server and to move the related files to that location.
If the specified database is mounted when this cmdlet is run, the database is automatically dismounted and
then remounted, and is unavailable to users while it’s dismounted.
This cmdlet can’t be run against replicated mailbox databases. To move the path of a replicated database, you
must first remove all replicated copies, and then you can perform the move operation. After the move operation
is complete, you can add copies of the mailbox database.
Note: A mailbox database can be moved, but before you proceed consider that the move requires the database
to be dismounted and taken offline, so it will not be accessible by your mailbox users during the move. This is
fine if the server has just been set up and there are no mailboxes on it, but if you’re moving a database with
active mailbox users a better option would be to create a new database on the new volume and perform
mailbox moves (which are non-disruptive to end users).
https://technet.microsoft.com/en-us/library/bb124742(v=exchg.160).aspx
Create a new database
Move the mailboxes
Create replicated database copies
https://www.vircom.com/blog/moving-an-exchange-server-2016-mailbox-database-without-disrupting-your-users-or-losing-data/
Agree with Stillme.
Since the Question clearly looking for “minimize downtime for users” and the options for Creation of mailbox database and moving the mailboxes is given, I feel the right options are
1. Create of New Database
2. Create replicated DB copies — recommended to create a copy before moving data (as the redundant copy must be available before the mailbox gets moved)
3. Move the mailboxes
This is a tough one. I think i’ll stick with my original answer. I appreciate your input!
Difference between real life and a test.
I would personally choose Stillme’s answer IRL.
Create a new database
Move the mailboxes
Create replicated database copies
But the questions states Ensure that multiple copies of the mailbox data are available at all times.
This answer does not allow for multiple copies of the mailbox data are available at all times it moves the mailbox removing the data from the original to the new database.
I also think the provided answer is incorrect. The question states Minimize downtime for the mailbox users. Moving the database of 500 users is going to take a really long time.
So is it possible to do it in this order?
Create a new database
Create replicated database copies
Move the mailboxes
This will allow for multiple databases at the same time when it is moved.
Also moving the mailboxes is done allowing less downtime then moving the entire database.
Create new db
MOUNT the db
Move the mailboxes
After creating you have to mount the db. Correct? Why does no one else mention this? I must be missing something…?
If not mistaken, when a new database is created it is mounted automatically and thus Mount should be replaced with replica creation as stated by NoBox and tmkreddy55.