350-901 · Question #90
Refer to the exhibit. What is the missing step in deploying a Docker container to IOx?
The correct answer is B. Build the package.yaml file. Deploying a Docker container to Cisco IOx requires building a package.yaml descriptor file that defines application metadata, resource requirements, and configuration for the IOx runtime.
Question
Exhibit
Options
- APull/Push the image to the Docker registry.
- BBuild the package.yaml file.
- CBuild the package.cert file to sign the app.
- DLog in to Device Manager.
How the community answered
(47 responses)- A4% (2)
- B83% (39)
- C11% (5)
- D2% (1)
Why each option
Deploying a Docker container to Cisco IOx requires building a package.yaml descriptor file that defines application metadata, resource requirements, and configuration for the IOx runtime.
Pushing the image to a Docker registry is not required for IOx deployment; ioxclient directly converts a locally present Docker image into an IOx package.
The package.yaml file is a mandatory IOx application descriptor that specifies metadata such as the application name, version, type, and required resources like CPU and memory. Without this file, the ioxclient tool cannot package the Docker image into the IOx-compatible .tar archive needed for deployment. This descriptor is what bridges the standard Docker image format with the IOx application lifecycle management system.
The package.cert signing certificate is used for optional application signing and is not a required step in the basic IOx container deployment workflow.
Logging in to Device Manager is a step that occurs after the package is built and transferred, not a step that is missing before or during the packaging phase.
Concept tested: Cisco IOx Docker container packaging and deployment steps
Source: https://developer.cisco.com/docs/iox/docker/
Topics
Community Discussion
No community discussion yet for this question.