In IBM Cloud Pak for Integration (CP4I) v2021.2, when App Connect Operator is deployed in a restricted network (air-gapped environment), access to external cloud-based services (such as AWS S3) is typically not available.
A restricted network means no direct internet access, so external storage services like Amazon S3 cannot be used to store Broker Archive (BAR) files.
BAR files contain packaged integration flows for IBM App Connect Enterprise (ACE).
In restricted environments, administrators must use internal storage options, such as:
Persistent Volume Claims (PVCs)
Ephemeral storage (temporary, in-memory storage)
Why Option A (S3 Cannot Be Used) is Correct:
B. Ephemeral storage cannot be used for BAR files. → Incorrect
Ephemeral storage is supported but is not recommended for production because data is lost when the pod restarts.
C. Only Ephemeral storage is supported for BAR files. → Incorrect
Both Ephemeral storage and Persistent Volume Claims (PVCs) are supported for storing BAR files.
Ephemeral storage is not the only option.
D. Persistent Claim storage cannot be used for BAR files. → Incorrect
Persistent Volume Claims (PVCs) are a supported and recommended method for storing BAR files in a restricted network.
This ensures that integration flows persist even if a pod is restarted or redeployed.
Explanation of Incorrect Answers:
IBM App Connect Enterprise - BAR File Storage Options
IBM Cloud Pak for Integration Storage Considerations
IBM Cloud Pak for Integration Deployment in Restricted Environments
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit