You have an Exchange Server 2013 organization.
You successfully migrate the public folders from a previous version of Exchange Server.
You discover that one of the public folder mailboxes almost reached its quota size.
You need to move some of the public folders in the public folder mailbox to another public folder
mailbox.
What should you run?

A.
Update-PublicFolderMailbox

B.
New-PublicFolderMoveRequest

C.
New-PublicFolderMigrationRequest

D.
Set-PublicFolderMailbox

Explanation:
* If the content of a public folder mailbox begins to exceed your mailbox quotas, you may need to
move public folders to a different public folder mailbox. There are a couple ways to do this. To move
one or more public folders that don’t contain subfolders, you can use the PublicFolderMoveRequest
cmdlets.
* Use the New-PublicFolderMoveRequest cmdlet to begin the process of moving public folder
contents between public folder mailboxes. Moving public folders only moves the physical contents
of the public folder; it doesn’t change the logical hierarchy. When the move request is completed,
you must run the Remove-PublicFolderMoveRequest cmdlet to remove the request or wait until thetime specified in the CompletedRequestAgeLimit parameter has passed. The request must be
removed before you can run another move request.
Incorrect:
Not A: Use the Update-PublicFolderMailbox cmdlet to update the hierarchy for public folders.
Not C: Use the New-PublicFolderMigrationRequest cmdlet to begin the process of migrating public
folders from Microsoft Exchange Server 2007 or Exchange Server 2010 to Exchange Server 2013.
Move a Public Folder to a Different Public Folder Mailbox