CI/CD pipeline basics in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a simple CI pipeline step

Consider a CI pipeline step that runs the following Node.js command to check the version of Node.js installed. What will be the output?

Node.js

node --version

A v20.0.0

B SyntaxError: Unexpected token

C Node.js version not found

D Error: command not found

💡 Hint

The command 'node --version' prints the installed Node.js version.

The command 'node --version' outputs the current Node.js version installed on the system, for example 'v20.0.0'.

🧠 Conceptual

intermediate

Purpose of a build stage in CI/CD

What is the main purpose of the build stage in a CI/CD pipeline?

A To compile source code and create executable artifacts

B To deploy the application to production servers

C To monitor application performance in production

D To write documentation for the project

💡 Hint

Think about what happens before testing and deployment.

The build stage compiles the source code and packages it into executable files or artifacts for testing and deployment.

❓ Troubleshoot

advanced

Troubleshooting a failing test step in CI pipeline

A CI pipeline runs tests using the command 'npm test' but fails with the error 'Cannot find module'. What is the most likely cause?

A The pipeline has no internet access

B The test files have syntax errors

C The Node.js version is too new

D The dependencies were not installed before running tests

💡 Hint

Think about what is needed before running tests in Node.js projects.

If dependencies are missing, tests fail with 'Cannot find module'. Installing dependencies with 'npm install' before testing fixes this.

🔀 Workflow

advanced

Correct order of CI/CD pipeline stages

Arrange the following CI/CD pipeline stages in the correct order from start to finish.

A 2,4,3,1

B 4,2,3,1

C 4,3,2,1

D 3,2,4,1

💡 Hint

Think about what happens first when a developer works, then what happens before deployment.

The correct order is: Commit code, Build, Test, Deploy.

✅ Best Practice

expert

Best practice for handling secrets in CI/CD pipelines

Which option is the best practice for managing sensitive information like API keys in a CI/CD pipeline?

A Send secrets via email to the deployment server

B Hardcode secrets directly in the source code

C Store secrets in environment variables managed by the CI/CD system

D Commit secrets to the public repository for easy access

💡 Hint

Think about security and automation in pipelines.

Storing secrets in environment variables managed securely by the CI/CD system avoids exposing them in code or logs.