Deployment

DVA-C02 · 72 questions

• A municipal Lambda deployment package omits a native library that exists on a developer's laptop, so production invocations crash on import even though local tests pass. What should the team ensure when preparing the artifact?
• A city permitting portal bakes stage-specific API base URLs into the built Lambda zip, so every environment change forces a full rebuild. What should the developers do?
• An ECS service that OCRs scanned municipal deeds should always run a known image from Amazon ECR in production. Which practice best meets that requirement?
• A SAM project for a county records API packs unit tests, Markdown docs, and multi-gigabyte sample media into the same directory that becomes the deployment bundle. What should the team change?
• A municipal DevOps policy says the test environment deploys from the develop branch while production deploys only from tagged releases on main. How should the team wire deployments?
• During council week, a PDF generation service on Elastic Beanstalk or ECS falls behind because tasks were sized with too little CPU. What should developers declare for the artifact?
• The city fees UI needs feature toggles that can roll out or roll back instantly without redeploying Lambda code. Which AWS capability best fits?
• Developers commit compiled nodemodules into Git so municipal deploys feel reproducible, but diffs are noisy and CI still sees platform skew. What is the better approach?
• For a grants intake stack, the team wants the Lambda function, API Gateway, and DynamoDB table versioned together. What should live in the application repository?
• Verbose debug logging is enabled in a shared config that currently ships in every package, including production. What should the team do for environment-specific configuration?
• A Lambda that preprocesses large GIS libraries for a parks department exceeds practical zip size and dependency constraints. Which packaging guidance should the team apply?
• CI installs different transitive dependency versions than developers' laptops, and Elastic Beanstalk deploys then fail. What practice prevents that drift?
• A .env.production file containing live database credentials was zipped into a CodeDeploy bundle for a civic payments API. What should packaging enforce?
• CloudFront caches a citizen portal's JavaScript aggressively, so releases sometimes leave browsers on stale bundles. How should the build artifact address this?
• A static park-map front end should give stakeholders a preview URL per Git branch. Which Amplify-oriented artifact approach fits?
• After deploying a permit API to the shared sandbox, engineers need confidence before asking QA for sign-off. What should they do next?
• CI tests for a municipal permit service call a third-party payment gateway and sometimes charge cards or fail when the vendor is down. How should integration tests be written?
• Developers need unfinished API routes isolated from citizens while QA still exercises a stable candidate. How should API Gateway stages be used?
• A stack update for the grants API must refresh staging without changing production parameters. What is the correct targeting approach?
• An EventBridge → Lambda → DynamoDB flow for license renewals needs confidence beyond unit-mocked handlers. What testing approach fits the deployed path?
• Mobile and backend teams agree on an OpenAPI contract for a city services app, and CI must fail if staging drifts. What should they automate?
• After each staging deploy of a citizen records API, the team wants a fast signal that the environment is basically healthy. What should they automate?
• Before pushing a grants Lambda that occupies the shared sandbox, a developer wants a quick local check with a fixture event. Which tool fits?
• A new ECS task definition revision for a document OCR service is ready. Where should it be verified before production?
• Staging tests for a licensing API currently cover only successful authenticated requests. What else must they include?
• QA accidentally pointed integration tests at the production DynamoDB table name through a wrong parameter. What must test environments ensure?
• A city transit telemetry team is writing unit-style consumer tests for a Kinesis Data Streams processor. Developers need repeatable, crafted records without waiting for live buses. What approach fits Domain 3 testing for streaming consumers?
• A county permitting app on Elastic Beanstalk ships a new version to staging. Health checks fail before anyone discusses a DNS cutover. What should the team do first?
• Two municipal developers work on separate feature branches for a parks reservation API. Both need to exercise SAM resources without overwriting the shared team development stack. What pattern should they use?
• A staging CloudFormation deploy for a clerk fee API reports CREATECOMPLETE, but the first runtime GetItem against DynamoDB fails with AccessDenied. Integration tests catch it before promotion. What does this validate about environment testing?
• A city inspection Lambda is invoked by API Gateway proxy events and by SQS. The team wants CI to invoke the function the same way every build. Where should the JSON test event payloads live?
• A township uses one OpenAPI definition for its business-license API across environments, but each stage must call a different backend. How should that be deployed?
• County integration tests must stay on an approved Lambda build while developers keep iterating on unpublished code. How should aliases be used?
• QA for a municipal containerized fee service must pull only images that passed vulnerability scans. Which tagging practice supports that gate?
• Product owners need to click through a new citizen self-service UI before merge. The front end is an Amplify app on a feature branch. What should they use?
• A multi-service recreation registration stack managed with AWS Copilot needs a place for QA sign-off on the approved build. What should host that candidate?
• Engineers add a new SQS queue and Lambda function for court-notice delivery to an existing SAM template. How should the change reach staging?
• Ops wants a CloudWatch alarm added to a nested application stack used by the city utilities portal in test—without manual console clicking. What is the preferred approach?
• A municipal API Gateway API has distinct stages for development, test, and production. Each stage must invoke a different Lambda alias. How should that wiring be managed?
• A developer uses Amazon Q Developer to draft unit tests for a pure municipal fee-calculation module, then plans the next step. What is the correct expectation?
• Every deploy to the city’s staging environment must prove the candidate build has not broken prior behavior before promotion. What pipeline gate fits?
• Before applying infrastructure changes for a library catalog service to the test account, CI should show what will change. Which CDK practice supports that review?
• After a test-environment deploy of a permit-write API, the pipeline should prove one critical path still works without leaving junk data. What should run next?
• API tests for a building-permit service need known rows in the test DynamoDB table before each run. How should that data be prepared?
• A developer removes a required JSON field from a city licensing API response. What should happen in the test stage before production?
• Only builds that passed the municipal test environment’s automated suite should be eligible for later promotion. How is that eligibility usually expressed?
• CI evaluates a SAM template for a utilities admin API and finds a security group that opens an admin port to 0.0.0.0/0. What should the pipeline do?
• Before open enrollment, a school-district registration API candidate must prove it can handle a surge in a pre-production environment. What test belongs there?
• Ops asks whether a new court-document Lambda for this release train should ship as a zip artifact from S3 or as a container image from Amazon ECR. What distinction should guide the choice?
• Citizens should reach the production licensing API at api.city.gov rather than the default execute-api URL, and that hostname must map to the prod stage. What configuration achieves that?
• A parameter increase for Lambda memory is required on an existing municipal SAM application. How should that change be released to the managed environment?
• A municipal permits team keeps development, test, and production CloudFormation stacks in separate AWS accounts with distinct parameter sets. What environment-management practice should they follow when promoting a release?
• A citizen-facing fee API must cut over with minimal downtime and a quick path back if errors spike. The team is choosing among blue/green, canary, and rolling for the next release. Which selection best matches a risk profile that needs an instant cutover with an idle prior environment ready?
• A county GIS portal team wants merges to main to start automated tests, deploy to an Elastic Beanstalk test environment, then wait for a human gate before production. Which approach implements that commit-triggered path?
• A city transit API pipeline must promote one build through test, staging, and production with approvals between stages. What CodePipeline practice ensures the same artifact moves across those environments?
• After a bad Lambda alias traffic shift for a municipal payments function, CloudWatch shows error spikes. How should operations roll back quickly using existing versioning?
• Release v2026.08.19 for a library catalog API must be auditable across Git and the deployment pipeline. Which release-management practice meets that need?
• A parks department API Gateway has stages for test and prod. Developers want each stage to invoke a different Lambda alias without cloning the entire API definition. Which feature provides that dynamic stage-to-backend binding?
• A containerized 311 intake service on ECS must cut over safely and keep the prior task set for a fast revert. Which blue/green approach fits?
• For a high-risk utility billing Lambda, the team wants only ten percent of API traffic on the new version for fifteen minutes before a full shift. Which deployment strategy should they configure?
• A weekday release for a multi-instance Elastic Beanstalk permitting site must replace instances gradually while keeping enough capacity online. Which strategy fits that platform constraint?
• Before any deploy stage for a municipal records API, unit tests and lint must run with cached dependencies. Which service should provide that CI build/test compute in the pipeline?
• Operations must push a revision to EC2, Elastic Beanstalk, ECS, or Lambda using a configured deployment strategy. Which AWS service is purpose-built to deliver that revision to those compute targets?
• A planning-department team already has Source, Build, and Deploy actions defined and needs them wired with a manual approval before production. Which service should orchestrate those existing CI/CD stages?
• Internal Python wheels for municipal GIS helpers must be installed during CodeBuild without relying only on the public internet. Which service should act as the private package repository?
• A classic multi-instance web app that issues building permits should run on a PaaS path with environment-level rolling updates. Which AWS deployment option best matches that application shape?
• Containerized citizen-notification workers must roll out by registering a new task definition on Amazon ECS. Which deployment action aligns with that platform?
• A city open-data front end uses Amplify. Production should publish from the main branch only after QA validates a preview branch. Which Amplify practice supports that?
• Infrastructure for a test-account permitting stack is defined in TypeScript with the AWS CDK. Which action applies that definition to the test environment?
• After staging metrics for a court-records API look healthy, production still needs a change-advisory human gate in the pipeline. What should the team configure?
• Production for a tax-portal release must deploy the exact build artifact that passed staging. Which practice preserves that guarantee?
• A stem asks the developer to invent an organization-wide multi-account DevOps platform topology before shipping a small civic API change. How should a DVA-C02 candidate interpret that task?