Cloud Native Fundamentals

1Z0-1084-26 · 33 questions

• A city permitting office relocates its long-lived JVM monolith onto OCI Compute instances with the same nightly patch cycle and shared in-memory session store. Which change would most clearly move the workload toward a cloud-native design?
• A municipal utility team wants every build of its meter-reading API to run the same way on a laptop, in a registry, and later on a managed cluster. Which packaging choice best expresses that cloud-native unit of delivery?
• A county records portal still runs three unrelated apps on one long-lived middleware host that operators patch in place after each CVE. What cloud-native deployment posture should replace that shared farm?
• A parks-and-recreation team wants the platform to keep three healthy replicas of its reservation API without an operator running start and stop checklists. Which cloud-native pillar describes that approach?
• During a late-night outage, a transit-authority developer finds a misconfigured runtime on a production host and is tempted to SSH in and edit files until the service recovers. Which immutable-infrastructure response is the cloud-native alternative?
• A water-department product team ships a billing microservice but still pages a separate operations group whenever the service misbehaves at 2 a.m. Which cloud-native principle are they missing?
• A library consortium containerizes its catalog app but still requires a stop-the-world release whenever any module changes, and operators cannot see why requests fail. What outcomes should the cloud-native pillars primarily unlock?
• A city open-data portal team wants high-impact configuration changes to feel routine instead of heroic overnight projects. Which approach best matches the cloud-native goal of frequent, predictable change?
• While reviewing a design for a municipal notifications service, an architect cites twelve-factor as guidance for portable, disposable processes with externalized configuration. How should that guidance be treated on the exam?
• A zoning-board API image embeds the production database URL and a plaintext password so “it just works” in prod. What twelve-factor-aligned fix should the team apply before promoting the same artifact to test and production?
• A 311 mobile backend keeps open case drafts and uploaded photos only in process memory and local container disk so responses stay fast. What risk does that create on a cloud platform that may stop or multiply the process at any time?
• A tax-assessment service hardcodes localhost Redis and a compile-time JDBC driver path so developers can run “everything on one laptop.” Which cloud-native adjustment treats those collaborators correctly?
• Each replica of a public-works work-order API writes its own dated log file under /var/log on the container filesystem. Operators cannot search one incident across replicas after a node is replaced. Which logging design matches cloud-native practice?
• A court-scheduling service takes several minutes of JVM warm-up before accepting traffic and ignores termination signals, dropping in-flight bookings when instances are replaced. Which disposability improvement should the team prioritize?
• After an emergency, an elections-office engineer edits binaries on the running production host so voters can keep checking polling locations. Why does that violate cloud-native build/release/run staging?
• Two municipal teams plan to integrate a license-renewal service with a payments service. They intend to code both implementations first and “document the URLs later.” Which API-first correction should they make?
• A city emergency-alert API must stay available if a single data-center event occurs, while callers need low latency and data residency in one geography. Which application-level placement approach best fits that goal on OCI?
• A housing-authority team labels “intake,” “inspection,” and “payments” as microservices but packages them as libraries loaded into one OS process so they can share memory. What essential microservice property have they lost?
• A DMV modernization program proposes services named “all database access,” “all UI widgets,” and “all batch jobs.” Which boundary approach better supports independent business change?
• A small parks department is still discovering its domain model for a new reservation system and currently ships weekly with one modular deployable. When is keeping a well-modular monolith the more honest choice?
• After splitting permit-review and fee-calculation into separate processes, developers propose a shared internal JAR of domain types so each side can call the other like a local method. What integration approach should replace that hidden coupling?
• In a city commerce platform, “price” means shelf list price in the catalog team’s model but means amount due after tax and fees in billing. Which decomposition tool should guide where to cut services?
• A reporting service on the inspections team starts issuing SQL against the licensing service’s tables to “avoid an extra API hop.” What persistence rule of microservice design does that break?
• Three municipal teams keep one shared database schema “to keep transactions easy,” so every migration needs a coordinated release window. What is the main design cost of that shared-schema anti-pattern?
• A waste-collection routing API adds a new optional ETA field for newer mobile clients but also renames a required stop-id field that older kiosk clients still send. Which evolution practice keeps independent deployability real?
• A city parking-fine service accepts payment callbacks that platforms may retry when the first response is lost. The handler currently charges the card on every invocation. What design change prevents double billing under at-least-once delivery?
• A municipal permit portal’s checkout must still return a useful response when the optional recommendations service is down. Which design approach best isolates that failure?
• A clerk waits on “is this SKU in stock?” while a separate nightly job fans a fee schedule change out to six interested services. How should those two interactions be designed?
• One city team wants Python for a GIS microservice while another prefers Java for billing, as long as the published HTTP contract stays stable. What makes that polyglot choice viable?
• During open enrollment, the city’s parcel-search service is the hotspot while permit submission stays quiet. What scaling approach fits independent services?
• A property-tax assessment update must write both the assessed value and the related lien flag in one commit, and both fields always change on the same release cadence. What should the team do about service boundaries?
• The city’s license API must introduce a breaking change to the permit payload. Independently deployed mobile and kiosk clients still call the current contract. What is the sound migration approach?
• After splitting a monolith, a city IT group wants each microservice to stay independently deployable. Which ownership model supports that goal?