Continuous Delivery Pipeline

Correct Answer: Parallelize test execution

Parallelizing test execution allows multiple tests to run at once, reducing the time required for the overall pipeline. Skipping code reviews, outsourcing, and canceling retrospectives have more implications on development than pipeline speed. Manual deployment processes might make the pipeline slower, and releasing with known issues may in fact create more work down the road.

Correct Answer: Integrate security scans into the pipeline starting from development and use repeatable processes across the environments

Integrating security scans into the pipeline starting from the development is the best approach. This not only ensures that any potential security issues are caught early on, but it also allows for repeatable processes across the environments, increasing the overall security. 'Ignoring the threats and continue with regular testing' is not a good option as it leaves the application vulnerable to attacks, doesn't aid in identifying the root cause of the threats and doesn't address the increased occurrence of threats. 'Outsourcing the application to a third-party company' could potentially leave the application even more vulnerable as control is given to another entity and it's not guaranteed that they'll prioritize security. 'Terminating the application' is also not an ideal solution as it completely stops the product from being delivered.

Correct Answer: Implement Feature Toggle

Feature Toggle allows selective enabling/disabling features, so that the troublesome commit can be identified faster and remedied. Skipping tests, delaying testing, or increasing interval between builds are counterproductive, potentially adding more errors/issues. Reverting the entire Sprint will lose beneficial work, and customer input won't directly address identifying the problematic commit.