During cloning, if the source environment has a hybrid Essbase version and the target environment is non-hybrid, what happens?

• A. The clone fails if the source has a hybrid Essbase version and the target is non-hybrid.
• B. The target is upgraded to match the Essbase version on the source.
• C. The clone succeeds with an upgrade
• D. The source Essbase version higher than target upgrades target to match

Answer: (A)

Cloning requires the target environment to support the same Essbase deployment type as the source. A hybrid Essbase version includes features and metadata structures that a non-hybrid target cannot accommodate. Because of this incompatibility, the clone is blocked to prevent an inconsistent system, so the operation fails when the source is hybrid and the target is non-hybrid. There is no automatic upgrade or on-the-fly conversion during the clone to reconcile this difference. To proceed, you’d need a target that matches the hybrid configuration (or a supported path to convert the target to hybrid before cloning).