Migration, Upgrade, and Multi-Site Management
Migration questions test planning and tooling knowledge. A candidate must understand the content transfer tool for moving content to Cloud Service, the pattern detector for identifying deprecated APIs, and the best-practice analyzer. Know the difference between an in-place upgrade and a migration, and how the repository restructuring (the move to /conf and /content) affects legacy projects. Understand how to migrate static templates to editable templates, and how to migrate client libraries and dialogs.
Key concepts include multi-site management: language copies, live copies, and blueprints. Know the difference between a language copy (translation) and a live copy (inheritance with rollout configurations), and how MSM rollout and inheritance work. Understand the role of the translation framework and connectors, and how to structure /content for multiple brands and locales. Also know the content fragment and experience fragment migration considerations.
Traps include confusing language copies with live copies, or assuming MSM inheritance is automatic for all properties (it is configured). Another trap is migrating content before code, or ignoring the pattern detector warnings. Expect questions on why a live copy breaks inheritance (manual edit or broken rollout config) and on how to handle shared content across sites without duplicating it. Also watch for questions that assume the content transfer tool migrates code; it migrates content only.
Rule of thumb: migrate code and configuration first, validate with the analyzer, then migrate content, and model shared content as live copies with rollouts. Worked example: a global brand with regional sites should use a blueprint and live copies with rollout configs, not duplicated pages.