Operations

CV0-004 · 51 questions

• City app servers for parking, licensing, and inspections write logs only to local disks, so ops cannot search a single incident across the fleet. What observability capability should the municipality configure first?
• Each microservice in the city’s citizen-account platform ships structured JSON logs that must be searchable in one place during outages. Which configuration best meets that need?
• Compliance requires the city to keep authentication logs for a defined period and then delete them. What should ops configure to balance that mandate with cost and privacy?
• A slow citizen checkout spans the API gateway, payments service, and notify service, and ops needs the path of one request end to end. Which observability approach should they use?
• Municipal dashboards for a tax portal should show CPU, request rate, and error rate over time—not only raw log lines. What should the operations team emphasize?
• When the city’s permit API error rate exceeds a threshold, on-call staff must be notified within minutes. What should ops configure?
• Night alerts flood the municipal on-call channel, and the team must rank which pages are urgent versus noise. What practice should they apply first?
• After triaging a water-billing outage alert, responders must mitigate the issue and keep stakeholders informed. What should guide that work?
• Without historical baselines, every CPU spike on the city’s GIS servers looks like an emergency. What should ops establish to make metrics and alerting meaningful?
• Developers want enough traces from the 311 app to debug issues without paying to store every request forever. Which design trade-off should ops apply?
• Security asks whether admin actions on the city’s cloud console are logged separately from noisy application debug spam. What should operations ensure?
• A black-box outage shows green VM metrics for the recreation portal, yet citizen journeys still fail. What observability insight should the team apply?
• Observability retention for the city’s multi-cloud estate is set to forever “just in case,” and storage cost is exploding. What should ops do?
• On-call receives an alert storm from one root failure cascading across municipal microservices. What observability practice reduces duplicate pages from that single incident?
• Peak permit season needs more capacity on identical web instances rather than enlarging a single box. Which scaling approach should the city use?
• A municipal database VM that cannot easily shard is saturating CPU and RAM. Which short-term scaling approach fits best?
• Autoscaling for the city’s library catalog API should react when average CPU trends upward over a monitoring window. What kind of scaling is that?
• The transit mobile backend should scale out when concurrent sessions or request queue depth crosses a load threshold. Which approach matches that requirement?
• A flood of IoT events from city sensors should spawn more consumer workers automatically. What scaling pattern fits?
• Every weekday at 7:00 before commute, transit apps need more capacity. Which scaling approach should ops configure?
• During a one-off election-night war room, ops needs extra capacity that automation was not designed to cover. Which scaling approach is appropriate?
• A stateful legacy permitting app cannot safely run multiple writers. Which short-term scaling choice is safest?
• When the city’s web tier scales in, active citizen sessions must not be cut mid-request. What should scale-in policies include?
• Municipal autoscaling flaps between scale-out and scale-in within minutes, thrashing instance counts. What stability control should ops add?
• A county permitting portal autoscales under load, but a runaway rule once spun up hundreds of instances overnight and exhausted the cloud budget. What scaling guardrail should operations set?
• A city recreation registration API sees heavy weekday traffic but almost none on weekends, yet the same peak capacity stays running Saturday and Sunday. What scaling approach best cuts idle cost?
• A municipal tax database team wants Sunday to capture a complete copy of the system, then weekdays to capture only what changed since the previous backup job. Which backup pattern matches that plan?
• Nightly county payroll backups must include every change since last Sunday’s full backup, not merely changes since last night’s job. Which backup type fits?
• A town hall keeps production VMs and all backup disks in the same on-premises rack. What backup placement best reduces the risk that one rack or site failure destroys production and backups together?
• Public-works cloud operators need fast restores for routine file mistakes and a separate path for regional disasters. How should they assign on-site versus geographically separate backup copies?
• A clerk of courts sets a recovery point objective of 15 minutes for the case-management database. What must backup or replication scheduling primarily satisfy?
• A city attorney places a legal hold on email related to a lawsuit, but the default backup policy purges sets after 30 days. What should operations do for the affected backups?
• A regional library consortium wants a database in another cloud region that continuously receives changes so failover is much faster than restoring from nightly backups. Which approach matches that need?
• A sheriff's office stores cloud backup images that could be stolen with the storage media. What control makes the backup data at rest unreadable to an unauthorized holder of that media?
• A county IT manager sees nightly backup jobs marked successful but worries the sets might not actually restore. What practice best proves recoverability?
• After a storage glitch, a municipal records team fears some backup objects may be silently corrupted even though catalogs still list them. What control best detects that integrity problem?
• During a planned maintenance window, utilities operators will restore a corrupted production volume by writing the backup directly onto that same volume. Which recovery approach is this?
• A city finance cloud team wants to restore a damaged ledger database, validate it thoroughly, then switch users over only after checks pass. Which recovery approach fits?
• After ransomware hits a department file share, the whole share must be recovered, while a separate ticket only needs one mailbox returned. What recovery capability distinction should the backup design support?
• A planning department asks cloud operations to keep every incremental backup forever with no purge. What should the response emphasize about retention?
• Critical CVEs are announced for guest operating systems used by a county's cloud VM images. What lifecycle action should operations take promptly?
• A municipal API platform vendor releases both a major version upgrade and a minor patch. What risk distinction should the change board expect?
• Before promoting a platform upgrade for the water-billing portal, what lifecycle step should operations complete first?
• Container workers for a parks permitting app use scratch disks that vanish when containers stop, but resident-uploaded documents must survive redeploys. How should data lifecycle be handled?
• A product used by city HR reaches vendor end-of-life and will receive no further updates. What lifecycle response is appropriate?
• A vendor ends security support for a middleware stack still running in a county integration tier. Why is continuing without a plan unacceptable?
• Decommissioning a retired municipal VM must be more than powering it off. Which checklist best reflects complete lifecycle teardown?
• New VMs for a city help-desk fleet keep launching from a six-month-old golden image that predates many critical patches. What image lifecycle practice should operations adopt?
• Temporary project sandboxes for a summer internship portal are still running months after the project ended and continue to accrue cloud charges. What lifecycle action is needed?
• A city GIS database runs on persistent block volumes attached to compute hosts that are scheduled for retirement next month. What must operations complete before those hosts are decommissioned?
• A municipal permitting portal must meet published citizen uptime SLAs while hosts need security patches. How should operations schedule the lifecycle changes?