C1000-138 practice question 7 of 15

How are Gateway extensions packaged to upload to the Gateways?

Full set: 60 questions

Answer options

A: As .tar files

B: As .cfg files

C: As .zip files Correct answer

D: As war files

Correct Answer:

C. As .zip files

Explanation

Gateway extensions for the IBM API Connect DataPower Gateway, such as custom policies, must be packaged as a single .zip file for upload. This archive must contain a specific directory structure that includes the policy implementation (e.g., GatewayScript files) and a policy.yaml manifest file that defines the policy's properties and metadata. The API Manager user interface provides the mechanism to upload this .zip file, which then makes the custom extension available for use within API assembly flows.

Why Incorrect

A. The required format is explicitly a .zip archive, not a .tar file, although both are archival formats.
B. A .cfg file is a generic extension for configuration files and is not the package format for deploying executable logic and metadata.
D. A .war (Web Application Archive) file is a standard package format for Java web applications and is not used for DataPower Gateway extensions.

References

- IBM API Connect v10.x Documentation, "Tutorial: Creating a custom policy", section "Packaging your policy". The documentation explicitly states: "Package the policy directory into a compressed .zip file." and "You upload the .zip file to API Connect by using the API Manager UI."

Question breakdown

Tests: Manage gateway extensions on a gateway service
Difficulty: Easy

Key idea: Gateway extensions are uploaded to a gateway service as a single .zip archive that contains a manifest plus the referenced configuration files.

How to reach the answer

The question asks about the package format used when uploading an extension.
A gateway extension bundles a manifest with DataPower configuration and other files.
Cloud Manager and the toolkit accept this bundle as a .zip archive.
None of the other formats is the accepted container, so C is correct.

Each option

AIncorrect. .tar archives are not the accepted format for gateway extension upload.
BIncorrect. A .cfg file may be included inside the archive, but it is not the upload package itself.
CCorrect. Gateway extensions are bundled and uploaded as .zip files.
DIncorrect. WAR files are Java web application archives and are unrelated to DataPower gateway extensions.

Common trap: DataPower configuration often lives in .cfg files, which makes B look plausible, but the .cfg is only one piece inside the zip.

In practice: Teams that need custom DataPower objects, such as user-defined policies or extra crypto config, package them with a manifest into a zip. They then attach it to the gateway service in Cloud Manager.

Remember: Gateway extension equals a .zip containing the manifest and its referenced files.

Drafted with AI assistance and checked against the answer key.

Keep practicing

Take the free C1000-138 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test