Docker automatically assigns names to containers using a combination of an adjective and a famous scientist ' s or hacker ' s name (e.g., clever_ritchie ). This naming convention is used to make container names more human-readable and memorable.

References: Docker Documentation - Container Naming

In a continuous delivery pipeline, artifacts are the final outputs produced during the build and integration stages. These artifacts are then deployed to different environments for testing and production.

Executable Applications : Artifacts can include executable files like .exe or .jar packages that are ready to be run.

Compiled Packages : Precompiled packages for installation via package managers (e.g., .deb or .rpm files) are suitable artifacts.

Docker Images : Docker container images encapsulate the application and its dependencies, making them ideal artifacts for consistent deployment across environments.

References:

Continuous Delivery

Artifact Repository

Content Delivery Networks (CDNs) are systems of distributed servers that deliver web content and media to users based on their geographic location. CDNs improve the performance and availability of content delivery.

Streaming Media : CDNs can handle and stream large media files, such as videos and music, efficiently to clients.

Multiple Locations : CDNs have servers in multiple locations around the world to serve content closer to users, reducing latency.

High Bandwidth and Low Latency : CDNs are designed to serve a large number of clients with high bandwidth and low latency, enhancing the user experience.

References:

What is a CDN?

How CDNs Work

REST (Representational State Transfer) is an architectural style for designing networked applications. It relies on a stateless, client-server, cacheable communications protocol -- the HTTP protocol. The main HTTP methods used in REST are:

GET : This method is used to retrieve data from a server at the specified resource.

PUT : This method is used to update or create a resource at the specified URL.

DELETE : This method is used to remove a specified resource.

The other options are not standard HTTP methods used in REST:

CREATE : This is not a standard HTTP method. The equivalent standard method for creating resources is POST .

REPLACE : This is not a standard HTTP method. The equivalent standard methods for replacing resources are PUT or PATCH .

References:

RESTful Web Services - HTTP Methods

MDN Web Docs on HTTP Methods

In Docker, the run subcommand is used to create and start a new container from an image. The full command typically includes the image name and any additional parameters needed to configure the container.

References:

Docker Documentation - run

Load balancers distribute incoming network traffic across multiple servers, improving the availability and scalability of applications. They help to ensure that no single server becomes overwhelmed, thereby enhancing the overall performance and reliability of the service.

Availability : Distributing traffic prevents any single server from becoming a bottleneck or point of failure.

Scalability : Adding more servers behind the load balancer allows the system to handle increased traffic.

Redundancy : Load balancers can be deployed in a redundant configuration to prevent them from being a single point of failure.

References:

Load Balancing - NGINX

AWS Documentation - Elastic Load Balancing

Service discovery is crucial in container environments to enable containers to find and communicate with each other. The common mechanisms for service discovery in container platforms include:

Environment Variables : Container platforms often set environment variables within containers to provide information about services. This method is simple and allows containers to access necessary details without additional configuration.

DNS Records : Many container platforms maintain DNS records that map service names to container IP addresses. This allows services to be discovered and accessed using standard DNS queries, which is a scalable and widely used approach.

The other options are not standard methods for service discovery:

A : There is no docker service discover command for service discovery.

C : Listing localhost ports in /etc/services is not a typical method used by container platforms.

D : Mounting sockets for all services into containers’ file systems is not a common practice for service discovery.

References:

Docker Documentation - Service Discovery

Kubernetes Documentation - Service Discovery

In Kubernetes, a Deployment manages ReplicaSets and ensures that the specified number of replicas for a given Pod is always maintained. If a Pod managed by a ReplicaSet is terminated (e.g., using the command kubectl delete pod < pod-name > ), the ReplicaSet detects the discrepancy in the desired state (number of replicas) and the actual state. As a result, the ReplicaSet will immediately create a new Pod to replace the terminated one and maintain the desired number of replicas.

Deployment Management : A Kubernetes Deployment is responsible for maintaining the desired state of Pods through ReplicaSets.

ReplicaSet Functionality : A ReplicaSet ensures that a specified number of Pod replicas are running at all times.

Pod Termination : When a Pod is terminated, the ReplicaSet notices the reduction in the number of running Pods.

Replacement Pod Creation : To restore the desired state, the ReplicaSet automatically creates a new Pod to replace the terminated one.

References:

Kubernetes Documentation - Deployments

Kubernetes Documentation - ReplicaSet