How are Gateway extensions packaged to upload to the Gateways?

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

1. The question asks about the package format used when uploading an extension.
2. A gateway extension bundles a manifest with DataPower configuration and other files.
3. Cloud Manager and the toolkit accept this bundle as a .zip archive.
4. 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.