Palo Alto Networks (PANW) Certified Cybersecurity Entry-level Technician (PCCET) Practice Exam

Which step of the CI/CD pipeline cannot be automated?

1. Coding

2. Integration

3. Testing

4. Monitoring

The correct answer is: Coding

In the context of a CI/CD (Continuous Integration/Continuous Deployment) pipeline, coding refers to the initial creation and writing of code by developers. This step typically involves human creativity, problem-solving skills, and specific knowledge of programming languages and application logic. While there are tools and environments that can assist with coding, such as IDEs (Integrated Development Environments), code suggestions, and linters, the actual act of writing code remains a fundamentally human-driven process that involves designing algorithms, creating architecture, and implementing features based on user requirements. On the other hand, the other steps—integration, testing, and monitoring—are more procedural in nature. Integration involves merging code changes into a shared repository, which can be fully automated using version control systems that manage code branches. Testing consists of running automated test scripts to ensure that the code behaves as expected, which is a common practice in CI/CD pipelines. Monitoring involves tracking application performance and health, often through automated tools that provide ongoing insights. Thus, while tools can facilitate and enhance the coding process, the creative and analytical aspects that go into writing code cannot be fully automated. This highlights the importance of the human role in the software development life cycle, making coding the step in the CI/CD pipeline that cannot be