Deploy and maintain data pipelines and workloads

DP-750 · 65 questions

• A city 311 medallion flow must ensure SLA metrics never read uncleansed tickets. How should stages be ordered?
• Housing needs reliable incremental SCD merges for eligibility history. Notebook DAG maintenance has become brittle. What should they choose?
• Transit must ingest AVL, then enrich, then publish—and later tasks must wait on earlier ones. How should the Lakeflow Job be designed?
• Public-health notebooks sometimes hit parse errors on clinic rows. What error-handling pattern should they use?
• A permits Lakeflow Job must not run the fee-publish task after a failed extract. What should be configured?
• Open-data wants a multi-task job of notebooks where profiling finishes before transform starts. What should they create?
• A water utility needs a managed graph for sensor bronze and silver tables with expectations attached. What should they create?
• Emergency management requires enrichment only after geocoding so alerts never publish without required coordinates. How should the pipeline enforce this?
• Library staff explore MARC cleanses in notebooks but need stable production MARC loads. How should tooling be split?
• A county API extract times out occasionally. Retries must not double-write successful gold publishes. What design is appropriate?
• A 311 job must keep human quarantine review separate from automatic gold publish. How should tasks be structured?
• Finance must stop before any MERGE when schema enforcement errors exceed a threshold. What pipeline behavior fits?
• Parks needs always-on incremental reservation facts plus a rare annual archive purge. How should pipeline styles be chosen?
• Courts must land sealed PDFs to a volume, extract metadata, load a Unity Catalog table, then share a restricted view. What order is correct?
• A city wants production hydrant inspection loads to carry durable quality rules rather than one-off notebook asserts. What should they prefer?
• A transit authority builds a ridership star schema job and must keep dimension loads ahead of fact publishes. What should the job DAG enforce?
• A housing authority needs a nightly eligibility SCD on Azure Databricks. What is the appropriate first job setup step?
• A 311 desk wants processing to start when new ticket exports land in cloud storage. Which Lakeflow Jobs capability should they configure?
• An open-data team must refresh published park facility tables every day at 02:00 local time. What should they configure?
• Public-health clinic ETL must notify on-call engineers if the job fails before morning rounds. What should they configure on the Lakeflow Job?
• A water utility streaming-adjacent job sometimes dies on transient network blips. What resilience setting should they enable?
• Courts need a cron-like docket publish that must wait until the CMS extract task finishes. How should the Lakeflow Job be designed?
• Transit needs notice when ridership backfill runs overrun the morning-rush reporting SLA. What alert should they use?
• A library production job must respect city cost guards instead of borrowing an oversized interactive cluster. What should job setup use?
• During a declared incident, emergency management needs weather-alert enrichment to keep running with minimal gaps. Which trigger mode fits best?
• Permits fee-publish jobs flood inboxes with success mail and bury real failures. How should alerts be tuned?
• A county pipeline hits a poisoned schema and keeps restarting overnight. What restart policy change is needed?
• A city wants the same notebooks to support daily runs and historical backfills by passing a rundate. What should the multi-task Lakeflow Job use?
• Housing needs a weekly full refresh and a nightly incremental eligibility path with clear ownership. How should jobs be bounded?
• Finance gold revenue publish failures must reach Azure Monitor–aware municipal ops. What practice should they follow?
• Parks must run a one-time fiscal-year rollover without changing the standing daily schedule. What should they do?
• A 311 production job must not reuse interactive development clusters that analysts keep busy. What isolation practice is correct?
• A city wants notebooks and pipeline definitions reviewed before production deploy. What SDLC practice should they apply?
• Transit engineers change AVL enrichment logic and need peer review before merge. Which Git workflow should they use?
• Two public-health engineers edit overlapping clinic transform notebooks and hit a Git merge conflict. What should they do?
• Housing wants confidence in SCD helper functions before they enter the eligibility pipeline. What testing step should come first?
• Open-data wants automated checks that sample CSVs land and silver schemas match in a dev catalog. What test type fits?
• Courts want confidence from CMS extract through gold calendar publish before promoting a change. Where should end-to-end tests run?
• A library plans to cut over catalog search extracts and needs staff confirmation the results look right. What testing gate should they include?
• A county wants repeatable deploys of workspace jobs and notebooks across environments. What packaging approach should they use?
• A city CI pipeline must deploy a Databricks Asset Bundle into the production workspace after merge. Which approach matches the Azure Databricks CLI deployment path?
• Emergency management wants the enterprise pipeline tool to push Asset Bundle updates without relying on an interactive CLI session. What should they use?
• A permits team wants production Databricks deploys gated so broken transforms never ship on merge alone. What should gate the deploy?
• A water utility needs hotfix branches for broken sensor parsers that do not block ongoing feature work. Which branching practice fits?
• A 311 Asset Bundle must point sandbox and production at different Unity Catalog catalogs without rewriting job logic. What should the team use?
• Finance wants peer review to catch both notebook logic and job orchestration changes before merge. What should reviewers examine together?
• Parks wants a lightweight integration test that proves a COPY INTO replay does not double picnic-permit rows. What should the test assert?
• A school-district CI must keep Azure Databricks CLI production deploys tightly governed. Which control is appropriate?
• After a quiet season, a city wants to rightsize workers for 311 Lakeflow Jobs based on measured use. What should they monitor first?
• A housing Lakeflow Job fails on a late eligibility task after upstream bronze and silver tasks succeeded. What recovery action fits best?
• Transit AVL enrich notebooks OOM during wide joins. Beyond hoping it stops, what should engineers tune?
• Public-health aggregations stall because a few giant clinic facilities dominate shuffle. What problem should they diagnose?
• Finance sees Spark UI spill-to-disk during year-end payment reconciliations. What does that signal, and what should they address?
• Open-data needs to find an expensive shuffle before gold citation publish. Which tooling path should they use?
• Permits silver applications accumulate many tiny files after heavy updates. Which Delta maintenance command should they run to compact?
• Courts finished retention-approved cleanup of obsolete bronze PDF path files and need to reclaim storage. Which command fits?
• A water utility wants Databricks/Spark diagnostic logs queryable alongside other Azure ops signals. What should they implement?
• Emergency management needs timely notice when Databricks job failure metrics rise during storm season. What should they configure?
• Library batch jobs cache a MARC landing set, but each run reads changing drops so cache hits stay poor. What should they conclude?
• A 311 query profile shows a shuffle-heavy join to a small category dimension. What mitigation fits?
• County analysis shows executor loss on a noisy-neighbor pool leaving a workload stuck. What operational response fits?
• A city wants lower cost and faster parking-citation dashboards by combining compute and Delta maintenance improvements. Which pairing fits?
• Housing discovers a runaway Lakeflow Job rewriting an entire gold table from a bad parameter. What control should they use immediately?
• Transit morning SLAs slip and ops has both Azure Monitor metrics and Spark UI stage data. How should they investigate?
• Public works must schedule OPTIMIZE and VACUUM without colliding with peak hydrant-inspection ingest. What planning approach fits?