70-332 · Question #4
You are moving a customized SharePoint site collection to a new farm. You attach and mount the source content database in the destination farm. You need to ensure that all customizations from the…
The correct answer is A. Install all custom applications in the destination farm. When migrating a customized SharePoint site collection via content database attach, all custom solutions and applications must be installed in the destination farm because custom code and features are stored in the farm, not in the content database.
Question
Options
- AInstall all custom applications in the destination farm.
- BCopy all custom master pages from the source site collection to the Style Library in the destination site collection.
- CCopy all SharePoint groups and users from the source farm to the destination farm.
- DCopy all custom master pages from the source site collection to the master page gallery in the destination site collection.
How the community answered
(30 responses)- A80% (24)
- B10% (3)
- C3% (1)
- D7% (2)
Why each option
When migrating a customized SharePoint site collection via content database attach, all custom solutions and applications must be installed in the destination farm because custom code and features are stored in the farm, not in the content database.
Custom SharePoint applications, solution packages (.wsp files), and features are deployed at the farm level and are not transferred with the content database. Installing all custom applications in the destination farm ensures the farm has the required features and assemblies to render and execute any custom code referenced by the migrated site collection. Without this step, pages or features dependent on custom solutions will fail to load.
Copying master pages to the Style Library does not make them functional, as customizations may depend on custom features, web parts, or solution assemblies that must be installed at the farm level.
SharePoint groups and user permissions are stored in the content database and are already migrated with the database attach; manually copying them is unnecessary and does not address missing customizations.
Master pages from a source site collection may already be in the content database, but without the underlying custom features and assemblies installed on the farm, copying master page files alone will not restore full functionality.
Concept tested: SharePoint content database migration with custom solutions
Source: https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/move-content-databases
Topics
Community Discussion
No community discussion yet for this question.