What does VIP portability mean?

• A. VIPs require separate deployment for each app.
• B. They must be built anew for every card.
• C. VIPs are portable in concept but only within the same environment.
• D. VIPs are portable; you can build an Integration Procedure once and use it everywhere.

Answer: (D)

VIP portability means you can design an Integration Procedure once and reuse it across different apps and environments. The idea is that the integration logic—how data is fetched, transformed, and acted upon—is packaged so it can be deployed to multiple orgs or contexts without rewriting. This enables consistent behavior, faster deployment, and less duplication because a single Integration Procedure can power multiple cards or use cases in different environments. The other options imply rebuilding or restricting reuse to a single environment, which goes against the portability concept.