Continuous Deployment - Quiz

"Capacity testing is a critical testing and helps to verify technical aspects."

Explanation:

Capacity testing is a type of performance testing that evaluates how a system performs under different loads to determine its maximum capacity. It helps in identifying:

• The number of users a system can handle before performance degrades.
• The hardware and software limits of the system.
• Potential bottlenecks in infrastructure, databases, or network components.

Since it focuses on technical aspects like system scalability, resource utilization, and response times, the correct answer is:

✅ "is a critical testing and helps to verify technical aspects."

✅ True

Explanation:

Environment configuration details can be integrated during build time, but it is generally not recommended for best practices.

At build time, configurations (such as database connections, API keys, or feature flags) can be baked into the build artifacts, but this approach has limitations:

• Requires a separate build for each environment (e.g., Dev, QA, Prod).
• Reduces flexibility in deploying the same artifact across multiple environments.
• Can expose sensitive information if not handled securely.

Best Practice:

Instead of integrating configurations at build time, it's better to:

• Use external configuration files or environment variables.
• Store secrets securely in vaults (e.g., Azure Key Vault, AWS Secrets Manager).
• Keep builds environment-agnostic to support Continuous Deployment (CD).

Thus, while True, it's not the best practice for modern DevOps workflows. ✅

People who perform the deployment should be involved in creating the deployment process because:

1. Better Understanding – They know the challenges and risks associated with deployment.
2. Automation Improvements – Their insights help in designing efficient and automated deployment pipelines.
3. Error Reduction – Involving them ensures that the process is well-documented and minimizes human errors.
4. Faster Issue Resolution – Since they understand the process deeply, they can troubleshoot deployment failures quickly.

Thus, the correct answer is:
✅ True

Dependencies between components in software systems are typically represented using a Directed Acyclic Graph (DAG). In a DAG:

• Nodes represent components or modules
• Edges represent dependencies between them
• The graph has no cycles, ensuring that dependencies do not create infinite loops

Why not "Cyclometric dependency"?

• Cyclomatic complexity is a measure of the number of independent paths in a program, not a direct way to represent dependencies between components.

Since DAG is the correct way to represent component dependencies, the correct answer is:
✅ "Directed acyclic graph"

Run-time dependencies are the libraries, frameworks, or other components that must be present when an application is executing in an environment. These include:

• Database drivers
• Third-party libraries (e.g., logging frameworks, API clients)
• Configuration files
• Runtime environments (e.g., Java Runtime, .NET CLR, Python interpreter)

Why not "Build time"?

• Build-time dependencies (e.g., compilers, linters, test frameworks) are needed only during development and compilation, not during execution.

Since an application needs run-time dependencies to function, the correct answer is:
✅ "Run time"

✅ "Integration pipeline"

The correct answer is:

"All of the Options"

Continuous Integration (CI) involves multiple tasks, including:

• Version Control (tracking code changes)
• Code Build (compiling the source code)
• Tests (running automated tests)
• Inspection (static code analysis and code reviews)

All these tasks ensure that new code integrates smoothly and maintains software quality.

False

Continuous Deployment (CD) is not mandatory to practice Continuous Delivery.

• Continuous Delivery ensures that the software is always in a deployable state, but the release to production is manual.
• Continuous Deployment automates the release process, deploying every change directly to production without manual intervention.

Thus, you can have Continuous Delivery without Continuous Deployment, but not vice versa.

The correct answer is:

"Smoke"

Smoke testing originated from hardware testing, where a device was considered to have "passed" if it did not catch fire or smoke upon first powering up. In software, it refers to a preliminary check to ensure that the basic functionalities work before deeper testing.

While Chef, Docker, and Kubernetes are widely used tools in configuration management and continuous deployment ecosystems, Photoshop is a graphics editing tool and has no role in managing configurations or deployments. Chef is a configuration management tool used to write infrastructure as code. Docker helps containerize applications along with their configurations, and Kubernetes manages these containers at scale. These tools work together to automate and streamline the deployment process. Photoshop, on the other hand, is designed for editing images and has no function in DevOps or software deployment pipelines.