What is the third key capability of VIPs?

• A. They must be recreated for each card.
• B. They are not portable between environments.
• C. They are portable; you can build an Integration Procedure once and use it everywhere.
• D. They require reconfiguration for each technology.

Answer: (C)

VIPs are designed to be portable across environments, so you can build an Integration Procedure once and use it everywhere. This means you create the integration logic in one place and deploy it across different cards and environments without re-creating or reconfiguring it for each setup. That reuse brings consistency and speeds up delivery. If you had to recreate for every card or reconfigure for every technology, you’d lose that efficiency, and claiming they aren’t portable would contradict the purpose of VIPs.