DevOps Fundamentals

CV0-004 · 30 questions

• A county platform team stores Terraform templates and application code and must prove who changed a production module and when. Which source-control capability primarily provides that history?
• Before a Terraform change that opens a new peering path for emergency services merges, a second city engineer must examine the diff. What source-control practice is this?
• A developer finishes a permitting-portal fix on a feature branch and wants discussion plus automated checks before the work joins main. Which collaboration mechanism fits?
• After committing locally, a city developer needs the shared team repository to receive those commits so colleagues can pull the latest work. Which source-control action accomplishes that?
• A cloud engineer finishes a local Terraform tweak for a parks subnet and wants a durable snapshot in repository history before sharing. What should they create?
• An approved feature branch for the city’s permit API has passed review; the team now needs those changes integrated into the main line. Which source-control operation does that?
• The transit authority’s cloud team insists new fare-calculator features be developed on short-lived branches instead of committing straight to production main. Why does branch management matter?
• A city release process still waits for a monthly weekend freeze, but leadership wants every commit to trigger automated build and test instead. What DevOps shift does this describe?
• Developers on the housing-vouchers service merge small changes into a shared mainline several times a day, each time running automated checks. Which CI/CD concept is this?
• Once the city’s pipeline verifies a build, the same automation releases the artifact to staging without waiting for a separate weekly install crew. Which concept does this highlight?
• In the municipal CI pipeline for a containerized licensing service, one stage compiles and packages the application before tests run. What is that stage called in CI/CD terms?
• The city’s pipeline refuses to promote a parks-map build when unit or integration tests fail. What role do those automated tests play?
• Before images from the tax-portal pipeline can deploy, the workflow runs container image scanning and secret detection. Why include those steps?
• A DevOps lead documents that every change for the court-records API must follow lint, then build, then test, then deploy with a manual approval before production. What CI/CD idea is this?
• Successful builds of the city’s microservice produce container images that later environments pull for deployment. What are those images in pipeline terms?
• Internal shared libraries for the city’s cloud apps must stay in a controlled package repository, while carefully vetted open-source dependencies may come from public registries. What distinction should the platform team enforce?
• A city permit office wants new applications to publish a message so scanners and citizen notifiers react on their own schedules without waiting on one shared call stack. Which integration approach best fits that loosely coupled design?
• County mobile inspectors need to create and read permit resources over HTTP using JSON payloads in a common modern API style. Which approach matches that requirement?
• A legacy regional planning partner still insists on XML envelope-style remote calls with a formal contract for municipal zoning exchanges. Which web service style are they most likely expecting?
• An internal city fee-calculator microservice needs another service to run a named calculation as if calling a remote procedure and return a result. Which integration pattern best describes that interaction?
• An emergency-dispatch console for the municipality needs bidirectional, low-latency updates between browsers and the cloud backend as unit statuses change. Which integration mechanism best fits?
• Civic open-data clients want to request exactly the nested fields they need from a flexible API schema instead of over-fetching fixed REST resources. Which API style addresses that need?
• A county platform team must choose between synchronous REST calls and asynchronous events for integrating a tax portal with downstream scanners. When is asynchronous event integration the better choice?
• Municipal ops wants agent-based or agentless configuration management that repeatedly enforces desired package and service state across fleets of VMs. Which tool category purpose should they prioritize?
• City developers need to package municipal apps with their dependencies into portable images that run consistently from laptop to cloud. Which tool purpose best matches that need?
• County SRE wants centralized log ingest, search, and dashboards so ops can troubleshoot multi-cloud municipal services from one place. Which stack purpose fits?
• A municipal engineering team needs distributed source history, branching, and a collaboration hub for application and infrastructure code. Which tool purpose is essential?
• Platform engineers want CI workflows defined next to municipal application code so pull requests automatically build and test. Which tool purpose fits best?
• City SRE wants time-series metrics dashboards and alert visualizations for municipal cloud workloads. Which tool purpose should they choose?
• A civic cloud team must repeatedly provision networks and instances with declarative templates, schedule containers across a cluster at scale, and run classic build jobs in a CI server. Which tool-to-job mapping is correct?