In which DevOps practice are manual processes replaced by automation for tasks like code compilation and testing?

Build Automation is the correct choice as it specifically refers to the practice of replacing manual processes related to code compilation and testing with automated solutions. In a typical development lifecycle, build automation tools manage the process of compiling source code into executable applications. This includes tasks such as gathering source files, compiling them, generating documentation, running tests, and creating the final build.

The primary purpose of build automation is to streamline the process of software development, ensuring that builds are produced in a consistent and repeatable manner, which not only saves time but also reduces the risk of human error. Automation tools can also provide instant feedback when issues are encountered during the build process, which enables developers to address problems more swiftly.

In contrast, while the other options involve automation in different aspects of the DevOps cycle, they do not focus primarily on the code compilation and testing stages. Configuration Management pertains to maintaining and overseeing system configurations, Deployment Automation deals with automating the deployment of applications to production environments, and Monitoring Automation relates to automating the tracking and analysis of application performance and system health. Each serves an important purpose within DevOps, but build automation is the dedicated process for handling the assembly and testing of code.