3. Identify the attributes of these application deployment types
📘Cisco DevNet Associate (200-901 DEVASC)
1. What are Containers?
Containers are a lightweight way to package and run applications along with all the resources they need, like libraries, dependencies, and configuration files.
- Unlike virtual machines, containers share the host operating system’s kernel but run in isolated environments.
- Think of containers as self-contained units that ensure an application runs the same anywhere — from a developer’s laptop to a cloud server.
2. Key Attributes of Containers
For the exam, you need to know the attributes that define containers:
- Lightweight and Fast
- Containers are smaller than virtual machines because they don’t include a full operating system.
- This makes them faster to start and stop.
- Isolation
- Each container runs independently from others on the same host.
- Problems in one container (like crashes or errors) don’t affect other containers.
- Consistency
- Containers package the application + all dependencies together.
- This ensures the application behaves the same way in development, testing, and production environments.
- Portability
- Containers can run on any system that has a container runtime, like Docker or Podman.
- This avoids the “works on my machine” problem.
- Scalability
- Containers are ideal for scaling applications because you can run many containers of the same app on different hosts quickly.
- They integrate well with orchestration tools like Kubernetes.
- Ephemeral Nature
- Containers are usually short-lived, meaning they can be created, used, and removed easily.
- Data stored in a container’s internal filesystem is lost when the container stops, unless external storage (like volumes) is used.
- Resource Efficiency
- Containers share the host OS kernel and resources, so they use CPU and memory more efficiently than virtual machines.
3. Container Components
When studying for DEVASC, you should know these components:
- Container Image
- A read-only template that contains the application and its dependencies.
- Example:
nginx:latestimage contains the Nginx web server ready to run.
- Container Runtime
- Software that runs containers on a host.
- Common examples:
- Docker Engine
- Podman
- Container Orchestration (Optional but Important)
- Tools to manage many containers at scale.
- Example: Kubernetes manages deployment, scaling, and networking of containers.
- Volumes and Networks
- Volumes: External storage for persistent data.
- Networks: Enable containers to communicate with each other or with the outside world.
4. Advantages of Containers
Containers are popular because they provide:
- Consistency across environments → Developers can test once and deploy anywhere.
- Rapid deployment → Containers start almost instantly.
- Efficient resource use → Multiple containers can run on a single host.
- Easy updates and rollbacks → Update an image and redeploy containers quickly.
5. Container vs Virtual Machine (Exam Tip)
You might see questions comparing containers and VMs:
| Feature | Container | Virtual Machine |
|---|---|---|
| OS | Shares host OS | Full guest OS included |
| Size | Lightweight, MBs | Heavy, GBs |
| Start-up Time | Seconds | Minutes |
| Isolation | Process-level | Full OS-level |
| Portability | High | Moderate (depends on hypervisor) |
6. Common Use Cases in IT Environments
- Deploy microservices (small independent applications) quickly.
- Run multiple versions of the same app for testing.
- Automate deployments in CI/CD pipelines.
- Host web servers, databases, and backend services in isolated containers.
✅ Key Points to Remember for the Exam
- Containers are lightweight, portable, and isolated environments for running applications.
- They share the host OS kernel, unlike VMs that need a full OS.
- Images + runtime + orchestration are the core concepts.
- They are fast, scalable, and consistent across environments.
- Persistent data requires volumes, because containers are ephemeral.
