Which cache key configuration would automatically invalidate the cache when the 'package-lock.json' file changes?

key: files: - package-lock.json

A team has a CI job that installs Python dependencies from a requirements.txt file. They currently use a static cache key, but they've noticed that sometimes the cache is stale after the requirements file changes. They want to ensure the cache is invalidated only when the requirements file changes, but they also want to avoid creating a new cache for every commit. Which cache key strategy should they use?

cache: key: "python-deps" paths: [.venv/]

cache: key: files: [requirements.txt] paths: [.venv/]

cache: key: $CI_PIPELINE_ID paths: [.venv/]

cache: key: $CI_COMMIT_SHA paths: [.venv/]

Which scenario best illustrates the use of a dependency in GitLab CI/CD?

A job sets an expiration time for files it produces

A job saves a compiled binary that is used by a job in a later stage

A job defines a cache key to reuse downloaded packages across pipeline runs

A job downloads a third-party library from a package registry before running tests

In GitLab CI/CD, what is the primary purpose of an artifact?

To pass job outputs, such as compiled files or reports, to jobs in later stages

To define environment variables for a job

To cache build dependencies between pipeline runs

To store external libraries downloaded from a package registry

GitLabCertified CI/CD Associate

Domain 3Objective 2

Objective: Use Artifacts and Dependency Caching GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 1)

Part of the Domain 3: Continuous Integration domain, which makes up ~24% of our current practice bank.

20questions here

4free pages

8concepts

Questions 1–5

1foundation · easy
Which cache key configuration would automatically invalidate the cache when the 'package-lock.json' file changes?
Select an answer first
2foundation · easy
Which keyword is used in a job definition to specify which files should be saved as artifacts?
Select an answer first
3expert · medium
A team has a CI job that installs Python dependencies from a requirements.txt file. They currently use a static cache key, but they've noticed that sometimes the cache is stale after the requirements file changes. They want to ensure the cache is invalidated only when the requirements file changes, but they also want to avoid creating a new cache for every commit. Which cache key strategy should they use?
Select an answer first
4foundation · easy
Which scenario best illustrates the use of a dependency in GitLab CI/CD?
Select an answer first
5foundation · easy
In GitLab CI/CD, what is the primary purpose of an artifact?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-CICD-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-CICD-ASSOCIATE” is a trademark of its owner, used for identification only.

Objective: Use Artifacts and Dependency Caching GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 1)

Questions 1–5

Which cache key configuration would automatically invalidate the cache when the 'package-lock.json' file changes?

Which keyword is used in a job definition to specify which files should be saved as artifacts?

Which scenario best illustrates the use of a dependency in GitLab CI/CD?

In GitLab CI/CD, what is the primary purpose of an artifact?

Keep studying — Domain 3: Continuous Integration