nerdexam
Microsoft

70-332 · Question #99

You recently upgraded from SharePoint Server 2010 to SharePoint Server 2013. You have not upgraded any site collections. You have a site collection that contains an InfoPath form library. The…

The correct answer is C. From Site Settings, navigate to Site collection health checks. When upgrading a SharePoint 2010 site collection to 2013, you must run health checks to identify potential content type conflicts before completing the upgrade.

Maintain a SharePoint environment

Question

You recently upgraded from SharePoint Server 2010 to SharePoint Server 2013. You have not upgraded any site collections. You have a site collection that contains an InfoPath form library. The InfoPath form library has a content type named CT1. You need to verify whether CT1 will conflict with any of the content types in SharePoint Server 2013. What should you do?

Options

  • AFrom Site Settings, navigate to Site collection upgrade.
  • BRun the Test-SPContentDatabasemcDiet.
  • CFrom Site Settings, navigate to Site collection health checks.
  • DFrom Site Settings, navigate to Content type publishing.

How the community answered

(45 responses)
  • A
    7% (3)
  • B
    11% (5)
  • C
    80% (36)
  • D
    2% (1)

Why each option

When upgrading a SharePoint 2010 site collection to 2013, you must run health checks to identify potential content type conflicts before completing the upgrade.

AFrom Site Settings, navigate to Site collection upgrade.

Site collection upgrade initiates the actual upgrade process rather than performing a pre-upgrade conflict analysis on content types.

BRun the Test-SPContentDatabasemcDiet.

Test-SPContentDatabase validates a content database for upgrade readiness at the database level, not for content type naming or ID conflicts within a specific site collection.

CFrom Site Settings, navigate to Site collection health checks.Correct

Site collection health checks, accessible from Site Settings, run a series of pre-upgrade diagnostic rules that identify content type conflicts, missing features, and other compatibility issues. This is the designated tool for detecting whether custom content types like CT1 will collide with built-in SharePoint 2013 content types. Running these checks before upgrading the site collection prevents upgrade failures caused by ID or name conflicts.

DFrom Site Settings, navigate to Content type publishing.

Content type publishing manages the propagation of content types from a publishing hub to subscriber site collections and does not perform conflict detection.

Concept tested: SharePoint site collection pre-upgrade health checks

Source: https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/run-site-collection-health-checks-in-sharepoint-2013

Topics

#content type conflicts#site collection health checks#InfoPath upgrade#post-upgrade verification

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-332 Practice