A company deploys managed customizations by using two solutions, SolutionA and SolutionB. The solutions share components with one another. A developer for SolutionA requires a new development…

Question

Options

• AImport SolutionA as managed and SolutionB as unmanaged.
• BImport SolutionA and SolutionB as unmanaged.
• CImport SolutionA as unmanaged and SolutionB as managed.
• DImport SolutionA and SolutionB as managed.

• A
  4% (1)
• B
  11% (3)
• C
  81% (22)
• D
  4% (1)

Explanation

The developer is working on SolutionA, so it must be imported as unmanaged - unmanaged solutions are fully editable and allow developers to create, modify, and delete components. SolutionB shares components with SolutionA but must not be modified by the SolutionA developer, so it should be imported as managed. A managed solution is read-only and locked; its components can be referenced but not altered directly. This isolation ensures that changes to SolutionA components do not bleed into SolutionB's customizations. Importing both as unmanaged (B) risks unintentional cross-solution edits. Importing SolutionA as managed (A or D) would prevent the developer from making any changes to it.

No community discussion yet for this question.