Which tasks are essential when merging multiple projects into a single project? (Choose three)

Question

Options

• AConsolidate folder structures
• BConfigure separate run modes for each project
• CStandardize naming conventions
• DTest the merged project in a staging environment
• EAutomate dispatcher cache configurations

• A
  83% (19)
• B
  13% (3)
• E
  4% (1)

Explanation

When merging multiple projects, you must consolidate folder structures (A) to eliminate conflicts and create a unified directory layout, standardize naming conventions (C) to ensure consistent file, variable, and asset naming across formerly separate codebases, and test the merged project in a staging environment (D) to catch integration issues before they reach production. These three steps address the core risks of a merge: structural chaos, naming collisions, and undetected breakage.

Why B and E are wrong: Configuring separate run modes (B) contradicts the goal of merging - you want a unified configuration, not preserved isolation. Automating dispatcher cache configurations (E) is an infrastructure optimization task unrelated to the merge process itself; it may be relevant post-merge, but it's not essential to the merge.

Memory tip: Think "CST" - Consolidate, Standardize, Test. These represent the three phases of any safe merge: organize the structure, unify the language/conventions, then validate the result.

No community discussion yet for this question.