Multiple FlexCard states are appropriate when the scenarios require materially different layouts, fields, or actions. A state controls what the user sees and does on the card under defined conditions. If each scenario has only minor visibility differences, conditional views on individual elements may be enough. However, when the layout and field set change significantly, separate states make the card easier to design, preview, debug, and maintain. Option A is inaccurate because states do not automatically create different data sources. Option C is false because conditional visibility can be applied to elements. Option B is directionally plausible, but the strongest design reason is the major layout and field difference. Salesforce Trailhead states that FlexCard states control displayed interactions/layouts and are useful when conditions affect several elements or different layouts.