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

Questions 6–10

1. 6application · medium

   A development team uses a monorepo with multiple independent services. They have a CI job that installs Node.js dependencies from a lockfile. They want to speed up the pipeline by caching these dependencies, but they are concerned that a change to the lockfile should invalidate the cache. Which cache configuration should they use?

   • Acache: key: "deps" paths: [node_modules/] policy: push
   • Bcache: key: files: [package-lock.json] paths: [node_modules/]
   • Ccache: key: $CI_COMMIT_SHA paths: [node_modules/]
   • Dcache: key: "node_modules" paths: [node_modules/]
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which statement accurately describes the lifetime of cache compared to artifacts?

   • ABoth cache and artifacts have the same expiration time
   • BCache can persist across pipeline runs, while artifacts are typically tied to a specific pipeline
   • CBoth cache and artifacts are deleted after each pipeline run
   • DArtifacts can persist across pipeline runs, while cache is tied to a specific pipeline
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A team's CI pipeline builds a documentation site. The build job generates many HTML files, but also includes a large temporary directory that should not be saved. They want to save only the HTML files and exclude the temporary directory. How should they configure the artifacts?

   • Aartifacts: paths: [public/] when: on_success
   • Bartifacts: paths: [public/] exclude: [public/tmp/]
   • Cartifacts: paths: [public/] expire_in: 1 day
   • Dartifacts: paths: [public/**/*.html]
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   Which practice is recommended to optimize pipeline performance?

   • AUse a static cache key for all jobs
   • BCache all files generated by a job
   • CAvoid using artifacts for passing outputs between stages
   • DCache only dependencies, not build outputs
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   What is a best practice for managing artifact size in GitLab CI/CD?

   • AAvoid creating large artifacts by only saving necessary files
   • BAlways save all files generated by a job as artifacts
   • CUse cache instead of artifacts for passing outputs between stages
   • DSet a very long expiration time for all artifacts
   Reveal Solution Discussion Select an answer first