nerdexam
Microsoft

70-332 · Question #22

You are migrating a SharePoint Server 2010 My Site collection to SharePoint Server 2013 by using the database attach method. You copy the content databases to the SharePoint 2013 farm. You need to…

The correct answer is B. Run the Windows PowerShell cmdlet Test-SPContentDatabase on the SharePoint 2013 farm. Before upgrading a content database in a database-attach migration, Test-SPContentDatabase must be run on the destination SharePoint 2013 farm to identify missing features, templates, or site definitions.

Maintain a SharePoint environment

Question

You are migrating a SharePoint Server 2010 My Site collection to SharePoint Server 2013 by using the database attach method. You copy the content databases to the SharePoint 2013 farm. You need to verify that all required objects have been successfully added to the SharePoint 2013 farm before upgrading the content database. What should you do?

Options

  • AIn the SharePoint 2013 site collection, run the site collection health checks.
  • BRun the Windows PowerShell cmdlet Test-SPContentDatabase on the SharePoint 2013 farm.
  • CRun the Windows PowerShell cmdlet Test-SPContentDatabase on the SharePoint 2010 farm.
  • DIn the SharePoint 2010 site collection, run the site collection health checks.
  • ERun the Windows PowerShell cmdlet Mount-SPContentDatabase on the SharePoint 2010 farm.
  • FRun the Windows PowerShell cmdlet Mount-SPContentDatabase on the SharePoint 2013 farm.

How the community answered

(36 responses)
  • A
    3% (1)
  • B
    78% (28)
  • C
    6% (2)
  • D
    11% (4)
  • F
    3% (1)

Why each option

Before upgrading a content database in a database-attach migration, Test-SPContentDatabase must be run on the destination SharePoint 2013 farm to identify missing features, templates, or site definitions.

AIn the SharePoint 2013 site collection, run the site collection health checks.

Site collection health checks in SharePoint 2013 can only run after the content database has already been mounted and the site collection is accessible, not as a pre-upgrade prerequisite check.

BRun the Windows PowerShell cmdlet Test-SPContentDatabase on the SharePoint 2013 farm.Correct

Test-SPContentDatabase checks a copied content database against the SharePoint 2013 farm's installed components and reports any missing web parts, features, or site definitions before the database is mounted or upgraded. It must run on the 2013 farm because it validates compatibility against that farm's specific configuration, allowing administrators to resolve gaps before committing to the upgrade.

CRun the Windows PowerShell cmdlet Test-SPContentDatabase on the SharePoint 2010 farm.

Running Test-SPContentDatabase on the 2010 farm validates the database against 2010 components, not the 2013 farm where the upgrade will actually occur.

DIn the SharePoint 2010 site collection, run the site collection health checks.

Running site collection health checks in the SharePoint 2010 farm only validates 2010 configurations and cannot verify whether the 2013 destination farm has all required objects.

ERun the Windows PowerShell cmdlet Mount-SPContentDatabase on the SharePoint 2010 farm.

Mount-SPContentDatabase actually attaches and initiates the upgrade of the database rather than testing for prerequisites, and running it on the 2010 farm is not valid for a 2013 migration.

FRun the Windows PowerShell cmdlet Mount-SPContentDatabase on the SharePoint 2013 farm.

Mount-SPContentDatabase mounts and upgrades the database rather than performing a pre-upgrade compatibility check for missing objects.

Concept tested: Pre-upgrade content database validation in SharePoint migration

Source: https://learn.microsoft.com/en-us/powershell/module/sharepoint-server/test-spcontentdatabase

Topics

#database attach upgrade#Test-SPContentDatabase#SharePoint 2013 migration#content database

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-332 Practice