Refer to the exhibit. A new application has just been developed as a Docker container. What is the missing step for packaging the container ready for deployment in IOx?

Question

Exhibit

Options

• APull/push the image to the Docker registry.
• BBuild the package.yaml files.
• CBuild the package.cert file to sign the app.
• DLog in to device manager and load the application.

• A
  13% (5)
• B
  77% (30)
• C
  3% (1)
• D
  8% (3)

Explanation

Packaging a Docker container for Cisco IOx requires creating a package.yaml descriptor file - the IOx metadata manifest that tells the ioxclient tool how to bundle the Docker image into a deployable .tar package. Without this file, ioxclient cannot generate the IOx application archive, making it the missing step between building the container and deploying it.

Why the distractors are wrong:

• A - Pushing to a Docker registry is a general Docker workflow step, not a required IOx packaging step; the image is typically built locally before bundling.
• C - A package.cert is not a standard required artifact in the basic IOx packaging workflow; signing is optional or handled differently.
• D - Loading the app via Device Manager is a deployment action that happens after packaging is complete, not part of packaging itself.

Memory tip: Think of package.yaml as the "recipe card" that tells IOx what ingredients (resources, ports, image) the app needs - you must write the recipe before you can serve the dish.

No community discussion yet for this question.