Microservices architecture breaks down applications into small, independent, loosely coupled services that can be developed, tested, and deployed independently.

Why does this improve release frequency? Each microservice can be updated, tested, and deployed on its own, reducing the risk and coordination overhead associated with monolithic releases.

This allows for faster feedback and more frequent delivery of value to users.

Extract-style reference:

“Microservices enable teams to deploy independently, reduce deployment risk, and increase release frequency by decoupling services.”

— Accelerate: The Science of Lean Software and DevOps , Chapter 4

PeopleCert DevOps Foundation v3.6: Stresses modular architectures for enabling rapid, independent deployments and continuous delivery.

Let’s clarify what these terms mean in DevOps:

Continuous Integration (CI): Developers integrate code into a shared repository frequently (ideally daily), with each integration automatically verified by tests.

Continuous Delivery (CD): Ensures software is always in a releasable state. Every change can be deployed to production, but the deployment itself may be a manual decision.

Continuous Deployment: Every change that passes automated tests is automatically deployed to production, without manual intervention.

Why is D (“Continuous Deployment requires a manual push button”) NOT TRUE?

Because Continuous Deployment is about no manual intervention —once code passes all tests, it’s automatically pushed live. Manual deployment is a feature of Continuous Delivery, not Continuous Deployment.

Extract-style reference:

“Continuous Deployment means that every change goes through the pipeline and is automatically put into production, resulting in many production deployments every day.”

— Accelerate: The Science of Lean Software and DevOps , Jez Humble & Nicole Forsgren

DevOps Foundation v3.6 distinguishes between Continuous Delivery (manual trigger) and Continuous Deployment (fully automated).

ChatOps is the integration of chat platforms with tools and workflows, allowing teams to manage operations and incidents directly through chat.

Using an API (Application Programming Interface) is the correct, scalable way to transfer incident-related data automatically from chat clients to ITSM (IT Service Management) tools, preserving traceability and reducing manual errors.

Why not manual cut/paste?

Manual processes are error-prone and slow; DevOps aims for automation and integration.

Extract-style reference:

“APIs enable seamless transfer of information between ChatOps platforms and ITSM tools, supporting automation, accuracy, and auditability in incident management.”

— DevOps Handbook ; ChatOps: Managing Operations and Collaboration in the Cloud , Jason Hand

PeopleCert DevOps Foundation v3.6: Promotes APIs for integration, automation, and collaboration.

ChatOps is the practice of conducting operational work directly through chat platforms (e.g., Slack, Microsoft Teams) integrated with automation and tooling. In this case:

Teams from multiple locations are collaborating in real-time via Slack.

They are running commands and queries directly from the chat to the delivery and monitoring systems.

This allows shared visibility, immediate context, and rapid action during incident resolution.

While A (Swarming) describes a collaborative incident response, it does not specifically imply integration with chat-based tools. C (Incident Management) is the overall process, and D (IT Support) is a function, but neither capture the specific ChatOps approach.

Thus, B – ChatOps is the most accurate answer here.