CI/CD pipelines facilitate "Automation," which speeds up the detection and resolution of errors by automating testing, deployment, and other tasks in the pipeline.

The primary purpose of using an SCM tool is to track and manage changes to the source code. It helps developers collaborate, maintain version history, and ensure code integrity.

The Waterfall Model is characterized by a linear sequence of phases, where each phase depends on the deliverables of the previous one. It's a rigid but systematic approach to software development.

In the "Throwaway" prototyping model, a developer creates a model that quickly represents only those aspects of the software that are of interest, with the intention of discarding it after gathering feedback and requirements.

The Requirements Phase in the SDLC is where the primary focus is on gathering, defining, and prioritizing the project's requirements, ensuring alignment with the desired product.

Balancing functional requirements with technical requirements is crucial to ensure that a software product is both feature-rich and performs optimally. It ensures the right balance between features and performance.

During the analysis phase of incident response, organizations examine the details of the incident to understand what happened and prepare a detailed report for documentation and future prevention.

Stress testing is a form of performance testing that assesses how a system behaves under increasing loads or stress. It often involves pushing the system beyond its specified requirements to identify performance bottlenecks and issues under heavy usage.

Blue-Green Deployment is suitable for deploying critical updates without downtime. It involves creating an identical environment and switching traffic once the update is validated, ensuring minimal disruption to users.

Monitoring and logging metrics like memory usage and CPU utilization are crucial to diagnose performance issues during peak usage. These metrics help identify resource bottlenecks causing slowdowns.