During cloning, if the source Essbase version is higher than the target version, what happens?

• A. If the source environment has an Essbase version higher than the target environment version, the clone process fails.
• B. The target Essbase version on the target is upgraded to match the version on the source.
• C. If the source environment has a hybrid version of Essbase and the target environment has a non-hybrid version, the clone process fails.
• D. If the source environment has a hybrid version of Essbase and the target environment has a non-hybrid version, the target environment is updated to hybrid Essbase.

Answer: (B)

Version compatibility drives cloning. If the source Essbase environment is on a newer release than the target, the clone process upgrades the target to match the source version. This ensures all objects, calculations, and metadata created on the newer engine are understood and executed correctly by the target. In other words, after cloning, the target runs the same Essbase version as the source, so there’s no version mismatch to cause incompatibilities. The other scenarios—such as the clone failing due to a version gap or conditional changes based on hybrid vs non-hybrid status—do not reflect how the upgrade is applied during a standard clone.