To display a FlexCard on an Experience Cloud (Community) page, the standard and required method is to use the FlexCard Player component. This component is a standard Lightning Web Component that acts as a host or container for the FlexCard. Within the Experience Builder, the developer drags the FlexCard Player onto the page canvas. Then, in the component's property panel, the developer must specify the API name of the created FlexCard in the "FlexCard Name" attribute. This configuration links the player to the specific FlexCard, enabling it to be rendered on the page.

A. The FlexCard designer's "Card Configuration" section does not contain a "Deployment" property to target specific environments like a Community.

C. The "Publish Options" within the FlexCard designer are used for settings like custom permissions or OmniScript support, not for setting a deployment target like "CommunityPage".

D. Component Visibility is a standard feature in the Experience Builder to control which users can see a component; it is configured after the component is already on the page, not for the initial deployment of the FlexCard itself.

1. Salesforce Official Documentation

OmniStudio: Add a FlexCard to a Lightning or Experience Page. The documentation explicitly states: "To add a FlexCard to a Lightning or Experience page

add the FlexCard Player component to the page in the Lightning App Builder or Experience Builder. In the component's properties

enter the name of the FlexCard..." This directly supports the correct answer.

2. Salesforce Official Documentation

OmniStudio: FlexCards. Under the "Activate and Deploy FlexCards" section

the process described involves activating the card and then placing it on a page using the appropriate builder (Experience Builder for communities)

which utilizes the FlexCard Player component.