- Courses
- Tutorials
- Practice
- Jobs
CI/CD Pipelines Using GitHub Quiz 4
Question 1
What makes GitHub Actions different from many traditional CI/CD tools?
- A
It only supports deployment workflows
- B
It requires external plugins for automation
- C
It only runs on Linux environments
- D
It is event-driven and tightly integrated with GitHub
Question 2
Which of the following is NOT a common event that can trigger a GitHub Actions workflow?
- A
push
- B
pull_request
- C
milestone
- D
commit_message_change
Question 3
In a GitHub Actions workflow, what is the primary purpose of the needs keyword in jobs?
- A
To define the operating system of a runner
- B
To pass secrets between jobs
- C
To create job dependencies and control execution order
- D
To cache dependencies
Question 4
Why is it considered a best practice to use GitHub Secrets instead of hardcoding credentials in workflow files?
- A
Secrets encrypt sensitive data and prevent exposure in logs
- B
Secrets allow workflows to run in parallel
- C
Secrets improve workflow execution speed
- D
Secrets automatically rotate credentials
Question 5
What is a key advantage of using self-hosted runners over GitHub-hosted runners?
- A
They automatically scale without configuration
- B
They provide access to private networks and custom hardware
- C
They eliminate the need for YAML workflows
- D
They only support Linux environments
Question 6
What is the main purpose of caching dependencies in GitHub Actions?
- A
To permanently store build artifacts
- B
To share data between different repositories
- C
To reduce workflow execution time by reusing dependencies
- D
To trigger workflows conditionally
Question 7
What happens when a GitHub Actions workflow uses a matrix strategy with multiple OS and language versions?
- A
Only one job runs using the latest configuration
- B
Jobs run sequentially for each configuration
- C
The workflow creates multiple parallel jobs for each combination
- D
The workflow fails if any configuration is invalid
There are 7 questions to complete.