The primary reason to version a FlexCard is to update it in place. When a new version of a FlexCard is created, modified, and then activated, it automatically replaces the previously active version across all Lightning pages, Experience Cloud sites, and other locations where it is embedded. This ensures that all instances of the component are updated consistently and simultaneously with the new changes, such as modified field labels. Cloning, in contrast, creates an entirely new and separate component that would need to be manually deployed to replace the old one in each location.

1. Salesforce Help

OmniStudio Documentation

"FlexCard Versioning and Cloning": "When you create a new version of a FlexCard and activate it

the new version becomes the active version everywhere the FlexCard is used. For example

if you have a FlexCard on a home page

and you create and activate a new version

the home page is updated with the new version." This directly supports option D.

2. Salesforce Help

OmniStudio Documentation

"When to Clone a FlexCard": "Clone a FlexCard to create a copy of the FlexCard that you can edit and use in a different context. For example

you have a FlexCard on an account record page

but you want a slightly different version on a contact record page." This confirms that the scenario in option A is suited for cloning.

3. Trailhead

Salesforce

"FlexCard Basics" module

"Manage FlexCards" unit: This unit explains the lifecycle of a FlexCard

noting that activating a new version makes it the current

live version

effectively replacing the old one. This reinforces the concept that versioning is for updating an existing

deployed component.