Continuous Delivery

AutoOps+ · 40 questions

• A city wants the new 311 web UI seen by only about 5% of citizen traffic before a wider rollout. Which delivery technique fits?
• The permits portal weekend release should swap citizen traffic from the live environment to a fully prepared standby in one cutover. Which strategy is that?
• Library catalog search pods must be replaced gradually so some healthy instances always serve patrons. Which deployment pattern applies?
• A single EMS reporting VM must be upgraded on the existing host rather than swapping to a parallel fleet. Which delivery approach is that?
• Municipal operators need the fastest traffic switchback if a tax-site release fails. Which strategy best prioritizes instant rollback?
• A small school-district cluster cannot afford to run a full duplicate green environment during upgrades. Which strategy fits the capacity constraint?
• Housing-portal canary traffic should grow only when error rate and latency stay within limits. What controls that expansion?
• After a tax-site blue-green cutover, why keep the prior (blue) environment as an idle standby?
• Transit API workers are updated with a rolling strategy. What should batch or surge settings ensure?
• An in-place upgrade is planned for a sealed public-health appliance with no parallel standby. What risk should operators accept?
• Citizen permit forms use sticky sessions, and a canary may skew results if the same users always hit one version. What caveat applies?
• Courts case-management plans a blue-green app swap, but the database schema is also changing. What caution still applies?
• Open-data API pods are rolled out gradually. How should new instances receive traffic only when ready?
• For a parks reservation app, how does a canary release differ from blue-green delivery?
• Before go-live of a new county payments page, operators must prove the site handles peak tax-season traffic. Which test type fits?
• After a clerk-workflow refactor, city IT wants proof that existing case-status and document-upload paths still work. Which test suite best catches those broken existing paths?
• Municipal ops needs confidence that a 311 intake change still works with the GIS parcel lookup service. Which testing approach best validates that cross-service behavior?
• Right after a library catalog deploy, the release engineer needs a fast check that search, hold, and login still respond. What should run first?
• Public-health IT wants ongoing proof that the health-portal login path stays healthy in production after releases. Which practice fits?
• Election-night reporting jobs fail and county IT must ship a fix quickly. Which continuous-delivery practice is appropriate?
• Post-deploy smoke tests for the public-works portal cannot create a work order. What should the delivery pipeline do?
• Before launching a text-to-911 pilot, the city must know the channel can handle expected peak message rates. Which QA activity applies?
• The permits portal calls an external payment provider during renewals. Which test best protects that municipal integration?
• A housing-authority casework bug needs an urgent hotfix. Auditors still expect a record of the change. What should operators do?
• City platform teams set an internal 30-day target that the 311 API succeed on at least 99.5% of requests. What kind of service-level concept is that?
• County email operations hold a written uptime commitment with the gateway vendor, including credits if availability falls short. What does that describe?
• Parks IT reports that the reservation site was available 99.9% of the month for citizen bookings. Which service-level idea is being measured?
• After a failed transit AVL deploy, leadership asks how long it typically takes to restore vehicle-location service. Which metric answers that?
• Library network ops tracks how long Wi-Fi controllers typically run between outages. Which reliability metric is that?
• Citizen reports about broken permit uploads are reviewed weekly and turned into backlog items for the next release. What continuous-delivery practice is this?
• Tax-portal reliability is within its monthly error budget, so product asks to ship a new filing feature this week. What service-level thinking supports that decision?
• A vendor email gateway misses its contracted uptime, while an internal 311 SLO miss only triggers a city team review. How should the AutoOps practitioner distinguish these?
• Municipal platform engineers want shorter outages after bad deploys of the clerk portal. Which practice most directly reduces MTTR?
• City IT announces a Sunday maintenance window for the assessor site and wants that planned downtime excluded from monthly availability. What service-level practice applies?
• City cloud deploys must use the provider CLI without leaving long-lived secrets on shared jump hosts. Which practice best secures that connection?
• Housing-authority automation jobs use a cloud SDK to update case queues. How should those jobs obtain credentials?
• CI must deploy a transit AVL update into the transit cloud account. Which IAM design is appropriate for the deploy role?
• Parks delivery pipelines currently inject static API keys from environment variables; security wants a stronger pattern for cloud deploys. Which comparison is correct?
• Municipal backups write assessor exports to object storage. How should the delivery pipeline authenticate to that storage?
• A legacy EMS uploader still uses long-lived IAM access keys. What hygiene step should AutoOps operators take?