Continuous Deployment - Quiz

False

Continuous deployment and continuous delivery are related but distinct practices.

• Continuous Delivery ensures that code is always in a deployable state, but the actual deployment to production may still require manual approval.
• Continuous Deployment takes it a step further by automatically deploying every change that passes automated testing directly to production.

You can practice continuous delivery without implementing continuous deployment, as continuous delivery allows for manual release decisions.

"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."

✅ "Acceptance"

Middleware configuration

✅ 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. ✅

✅ "Smoke"

Explanation:

Smoke testing was originally derived from hardware testing, where a device was powered on for the first time, and if it started smoking or failed immediately, it was considered defective.

In software development, smoke testing refers to a preliminary test performed after a build to check if the critical functionalities are working before moving to deeper testing. It ensures that:

• The application build is stable enough for further testing.
• Major functionalities are working as expected.

Thus, the correct answer is:
✅ "Smoke"

Traceability – CM tracks and records changes, ensuring that every modification is documented and can be traced back to its origin.

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

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"