When deciding how to deploy changes to a FlexCard, which scenario best justifies versioning instead of cloning?

When deciding how to deploy changes to a FlexCard, which scenario best justifies versioning instead of cloning?

• A. The new version of the FlexCard will be used in a new Console, and the current version should remain unchanged.
• B. Another team member is developing new action, fields and styling for the current version of the FlexCard.
• C. The new and current versions will be displayed together on the same target.
• D. All instances of the FlexCard must be updated with the changes.

Answer: (A)

Versioning lets you create a new version of the same FlexCard and deploy that version separately from the one already in use. This is ideal when you want to ship changes to a new Console while keeping the current Console running the existing version, so the old behavior remains unchanged and risk is minimized during the rollout. In this scenario, the new version will be used in a new Console and the current version should stay untouched. That exactly aligns with the purpose of versioning: isolate the new work from the existing card and control where and when the new version is active. Cloning creates a separate card copy rather than a new version of the same card, which is more about duplicating for independent use rather than preserving and evolving a single card across targets. The other situations describe either showing two variants on the same target or updating all instances, which don’t leverage the versioning approach as cleanly for this purpose.

Versioning lets you create a new version of the same FlexCard and deploy that version separately from the one already in use. This is ideal when you want to ship changes to a new Console while keeping the current Console running the existing version, so the old behavior remains unchanged and risk is minimized during the rollout.

In this scenario, the new version will be used in a new Console and the current version should stay untouched. That exactly aligns with the purpose of versioning: isolate the new work from the existing card and control where and when the new version is active. Cloning creates a separate card copy rather than a new version of the same card, which is more about duplicating for independent use rather than preserving and evolving a single card across targets. The other situations describe either showing two variants on the same target or updating all instances, which don’t leverage the versioning approach as cleanly for this purpose.