Test your CircleCI knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is a "workflow" in CircleCI, and how does it relate to jobs?
In this round
What is a "workflow" in CircleCI, and how does it relate to jobs?
What is the purpose of "parallelism" in CircleCI (the `parallelism` key on a job)?
What is a common reason a CI pipeline (CircleCI or otherwise) might use "fan-out, fan-in" workflow structuring?
What does a "manual approval" job (using the `type: approval` job type) do in a CircleCI workflow?
What is the standard configuration file name and location CircleCI looks for in a repository?
What is a CircleCI "orb"?
What does defining a `command` (a reusable command, distinct from a built-in step) in CircleCI 2.1+ config allow you to do?
What is the difference between a workspace and a cache in CircleCI?
Why might a team prefer running expensive integration/end-to-end tests only on a schedule (e.g. nightly) or only pre-merge on `main`, rather than on every single commit/PR?
What is "caching" used for in a CircleCI pipeline (e.g. via the `save_cache`/`restore_cache` steps)?
What does the `requires` key do when defined on a job within a CircleCI workflow?
What is the "config.yml" `version` key (e.g. `version: 2.1`) used for?