Implement and manage an analytics solution

DP-700 · 67 questions

• A national museum and archives network wants its Fabric admin to group every conservation-telemetry workspace across all branches under one shared policy classification in the Fabric admin portal, separate from billing and separate from item labels. Which capability should the admin use?
• Heavy month-end Warehouse queries in the museum network's ticketing-and-finance workspace are causing Eventhouse queries against gallery conservation telemetry in a different workspace to slow down, because both workspaces currently draw compute from the same Fabric capacity. What should the Fabric admin do to isolate the two workloads?
• PySpark notebooks that clean up OCR text from digitized oral-history transcripts keep waiting a long time to start because they're competing for the workspace's shared starter pool, and the team needs a guaranteed node size for this job. What should be configured in the workspace's Spark settings?
• A conservation branch in a different region reads digitized-object images through a OneLake shortcut pointing at an external storage account in the original region, and staff complain that repeated reads of the same images are slow. Which workspace-level OneLake setting addresses this?
• A data engineer wants to stand up an Apache Airflow Job in the museum network's archives workspace to host DAG code, and needs to size the compute backing those DAG runs before the item is created. What must be configured in the workspace's Apache Airflow settings first?
• The archives development team wants every change to Fabric items in their digitization workspace tracked with commit history and reviewable before it takes effect, rather than edited directly with no record. What should they set up?
• The team maintaining the ticketing-and-finance Warehouse wants schema changes reviewed and version-controlled the same way application code is, with build validation before changes are deployed, rather than relying only on manual T-SQL scripts. Which Fabric lifecycle-management capability fits?
• After validating a new digitized-collection Lakehouse notebook in the Test stage of a deployment pipeline, the team is ready to make it live for the whole museum network. What is the correct next action?
• A branch curator without domain-admin rights tries to assign their branch's Lakehouse workspace to the network's shared "Collections" domain in the admin portal, but the option is unavailable to them. Why?
• The museum network built its new ticketing Warehouse on a Fabric trial capacity during a pilot, and the trial is about to expire before the exhibit season begins. What should the Fabric admin do to keep the workspace running without interruption?
• Several oral-history transcript-cleaning notebooks in the archives workspace each spin up their own Spark session, and the team wants multiple notebooks to share one running session to cut both startup time and cost. What Spark setting accomplishes this?
• After several teams began linking to a shared external "digitized-manuscripts" storage account through OneLake shortcuts, the archives network's OneLake storage consumption rose noticeably, and the admin wants to reduce that footprint even if it means slightly higher read latency. What should be changed?
• A data engineer tries to create a new Apache Airflow Job item inside a branch archives workspace, but the item type doesn't appear as an option. What is the most likely missing prerequisite?
• An engineer wants to build and test changes to a digitization-pipeline Lakehouse notebook without touching the content that's live in the shared production workspace, which is connected to the main Git branch. What is the recommended approach?
• Two engineers independently modified the ticketing-and-finance Warehouse schema in their local database project files, and the project lead wants to catch any conflicting changes before either set is published to the live warehouse. What should the lead do?
• After a pipeline item is promoted from the Test stage to the Production stage of a deployment pipeline, it should point to Production's own Lakehouse rather than the one used in Test, without anyone manually editing the connection after every deployment. What should be configured?
• The Fabric admin wants every workspace grouped under the network's conservation-branch domain to default to the same Spark pool configuration, without visiting each workspace individually to set it up. What should the admin configure?
• At the end of the quarter, the archives network needs extra Spark compute for a backlog of PySpark jobs cleaning up scanned-document OCR output on the digitization Lakehouse, and wants to reduce spend again once the backlog clears, without moving any workspace to a different capacity. What should be done?
• Every engineer working on oral-history transcript cleanup currently installs the same set of PySpark text-processing libraries by hand inside each new notebook session, which wastes time and occasionally produces mismatched versions across notebooks. What workspace-level Spark setting fixes this?
• Two branch archives workspaces both run near-identical Apache Airflow DAGs for similar workloads, but one branch's DAG runs consistently finish much faster than the other's. An engineer suspects the difference comes from how each workspace's Apache Airflow settings are configured. What should be compared?
• A teammate updated the connected Git branch for a Lakehouse notebook while another engineer separately edited the same notebook directly inside the workspace, and syncing now shows the two versions cannot merge automatically. What must the engineer do?
• Before promoting a batch of item changes from the Test stage to the Production stage during a major exhibit launch, the pipeline owner wants to review exactly which items differ between the two stages first, rather than deploying blind and rolling back if something breaks. What should they do?
• After Fabric rolled out a new default Spark runtime version tenant-wide, PySpark notebooks that clean oral-history transcripts and depend on an older library API start failing intermittently. The team wants to pin the workspace to the previous runtime version until the notebooks are updated. What should be changed?
• A national archives network is standing up a new Fabric workspace for its digitisation program. One engineer needs to be able to change which Fabric capacity the workspace runs on and adjust workspace-wide settings, while everyone else on the team only builds pipelines and reports. Which workspace role must that engineer hold?
• An outside conservation scientist needs to run queries against one specific Lakehouse holding gallery humidity and vibration telemetry, but the archives network does not want to make her a member of the workspace or expose any other item in it. What should the data engineering team do?
• A shared Lakehouse holds both public collection-catalogue tables and a table of embargoed donor bequest details. A research-partners group should be able to query the public tables through OneLake but must never see the embargoed table, and giving them a separate copy of the Lakehouse is not an option. What should the team configure?
• Curators at each of the archives network's regional branches should see only the inter-branch loan records for their own branch when they query a shared Warehouse table, based on their signed-in identity, with no separate table per branch. Which security feature should the team implement on the table?
• An oral-history metadata table in a Fabric Warehouse includes a column with interview subjects' home addresses. Research analysts need full access to every other column in the table but must be completely blocked from ever retrieving values from the address column. What should the team configure?
• A Warehouse contains a staging table used only by the nightly ETL process to hold raw, uncleaned ticketing data before transformation. Analysts should never see this table in their tool of choice, but the pipeline must keep reading and writing to it. Which security mechanism directly hides the entire table object from analysts?
• A Lakehouse's Files section stores raw scanned images from digitisation runs. One subfolder holds scans of documents tied to an embargoed donor bequest, sitting alongside otherwise-unrestricted digitisation exports in the same Files area. The team needs to restrict just that subfolder, without touching any Delta table permissions. What should they configure?
• Front-line ticketing analysts at a national museum need to review visitor payment records but should see donor and visitor credit-card numbers only as a partially obscured value, such as the last four digits, while the finance team continues to see full numbers. Which feature should the team apply to the card-number column?
• Compliance wants a protection marking attached to Fabric items containing culturally restricted donor records, so that if an analyst exports the data to an Excel file, the same protection (such as encryption or access restriction) travels with the exported file. Which feature accomplishes this?
• A regional archivist wants to flag a well-built semantic model of collection-visit statistics as an organization-wide trusted source, a status that requires review and approval by a designated authority before it can be applied — not something the item's owner can simply switch on. Which endorsement level is this?
• Compliance needs a record of every time a specific Lakehouse holding embargoed donor records was opened, and by which accounts, to satisfy a retention audit. Where should the archives network's security team look for this activity trail?
• A team just created a new Lakehouse for scanned-document metadata and has not yet defined any custom OneLake data access roles on it. Before any custom role is configured, what access does a user who already has item-level permission on the Lakehouse have to its data through OneLake?
• A workspace role such as Contributor governs broad capabilities like creating and editing items across an entire Fabric workspace. A museum volunteer who is not a member of that workspace at all still needs to open one specific report. Which mechanism grants her access to just that report without making her a workspace member?
• A data engineer proposes handling branch-based row restrictions by adding a filter to each Power BI report visual instead of implementing row-level security on the underlying Warehouse table. Why is enforcing the restriction at the database layer, rather than in each report, the correct approach?
• An engineer needs to lock down a single donor-SSN column on a Warehouse table so one security group can never retrieve it, while every other column in the table stays fully accessible to that group. How is this restriction actually configured in a Fabric Warehouse?
• A Contributor reports that a staging table used by the nightly ETL job no longer appears anywhere in the Warehouse's object list for their account, even though they can still see and query every other table. What is the most likely, and expected, cause?
• A folder-level restriction was applied to the embargoed-bequest subfolder inside a Lakehouse's Files section. An engineer later notices that a new sub-subfolder created inside it is still visible to users who were denied access to the parent folder. What should the engineer check first?
• An analyst has been granted read access to a ticketing table with dynamic data masking applied to the card-number column, but her queries still return the masked pattern instead of full values, even though her manager insists she needs to see real numbers for reconciliation. What is most likely missing?
• A Lakehouse holding culturally restricted oral-history transcripts carries a sensitivity label indicating restricted donor content. Compliance is surprised to find that an analyst with edit permission on the item was still able to modify the transcript data despite the label. What explains this?
• An item owner opens the endorsement settings on her semantic model of visitor-flow statistics, hoping to mark it Certified so other branches can trust it, but the Certified option is unavailable to her even though she has edit permission on the item. What is the most likely reason?
• The archives network's compliance office wants a consolidated, tenant-wide view of Fabric item-access activity across every branch's workspace, exportable into their existing security monitoring system rather than reviewed manually workspace by workspace. What Fabric governance capability supports this?
• Governance leadership wants one consistent data-access rule enforced no matter whether a branch analyst queries a Lakehouse's tables through the SQL analytics endpoint, a Spark notebook, or a Power BI report, rather than configuring the restriction separately in each engine. Which Fabric capability is designed to provide this consistency?
• The archives network's data engineer has a PySpark notebook that cleans OCR text from scanned oral-history transcripts every night. She currently opens the notebook and runs it by hand. She wants the cleanup to run automatically each night, retry once if it fails, and appear in the same run history as the rest of the nightly load. What should she do?
• A curator with no coding background needs to pull nightly ticket-sales totals from the museum network's box-office SaaS system into a Lakehouse, applying a few simple filters and renaming columns along the way. No PySpark or SQL skill is required for the task. Which tool should the data engineering team hand her?
• The museum network's digitisation lab finishes scanning the day's incoming objects at 1:30 a.m. every night, after the loan-return dock closes. Leadership wants the ingestion pipeline to start automatically at 2:00 a.m. every night without anyone manually kicking it off. What is the simplest way to make that happen in Fabric?
• Donors and community elders upload oral-history recordings to a OneLake landing folder whenever their individual interview sessions happen to finish, sometimes twice a week and sometimes three times in one day. The archives team wants transcription processing to start as soon as a new recording lands, without waiting on a fixed clock. What kind of trigger fits this pattern best?
• A conservation team wants a curator-maintained Dataflow Gen2 to do light cleanup on daily humidity-sensor exports, followed by a PySpark notebook that performs heavier statistical aggregation before the results land in the Lakehouse. They want both steps to run as one dependable, monitorable nightly flow rather than two separately scheduled items. How should this be orchestrated?
• A pipeline copies newly digitised object records into a Lakehouse and then runs a notebook that reformats them for the public collections catalog. The archives team wants a Teams alert sent to the on-call engineer only if the copy step fails, and the reformatting notebook should never run against a failed copy. How should the activity dependencies be configured?
• A national museum network has twelve branch locations, and the loan-tracking pipeline needs to run the same copy-and-notebook sequence once per branch every night, pulling each branch's own loan data by branch code. Building and maintaining twelve nearly identical pipelines is proving painful. What orchestration pattern reduces this to one pipeline?
• A nightly pipeline ingests scanned-document images from a dated folder structure, where each night's folder is named after that day's date. Rather than hardcoding a specific date into the Copy activity's source path every day, the data engineer wants the path to update itself automatically based on when the pipeline runs. What should she configure?
• A pipeline's Copy activity pulls conservation sensor telemetry from a third-party gallery-monitoring API that occasionally throttles requests and returns a transient error for a few seconds before recovering. Right now, any throttling event causes the whole nightly pipeline to fail and require a manual rerun. What should the data engineer configure on the Copy activity to handle this gracefully?
• A data engineer is designing a nightly flow that ingests visitor-ticketing data, checks whether the branch is open that day, and then either loads the data normally or skips loading entirely on days the branch was closed for a private event. Multiple branching decisions and a multi-step sequence are involved. Where should this control-flow logic live?
• An exhibit loan return at one branch might happen any day of the week, sometimes early morning, sometimes late at night, whenever the receiving branch finishes intake paperwork. The archives team wants downstream cataloguing to start the moment the loan-return record appears, not on some fixed clock. Which orchestration approach is the better conceptual fit here?
• A pipeline's Dataflow Gen2 activity, which cleans up daily gift-shop sales exports, fails partway through most nights without anyone noticing until a weekly report looks wrong. The team wants to be notified the same night it happens. What is missing from the pipeline?
• A pipeline uses a ForEach activity to run a copy-and-notebook sequence once per branch across all twelve museum branches. Once every branch has finished, a final notebook needs to run a single aggregation across all twelve branches' results together. Right now the aggregation notebook sometimes starts before every branch iteration inside the ForEach has finished. What is the underlying orchestration mistake?
• During the network's annual winter closure week, several branches don't open at all, and their ticketing-ingestion steps should simply be skipped for that week without disabling the entire nightly pipeline for every other branch. What orchestration approach handles this most cleanly within a single pipeline?
• A newer data engineer on the archives team asks a colleague to explain, in plain terms, what fundamentally separates a schedule trigger from an event-based trigger in Fabric orchestration. What is the correct plain-language distinction?
• A pipeline's nightly schedule trigger, configured months ago to fire at 2:00 a.m., appears to have started firing at 3:00 a.m. instead ever since the clocks changed for daylight saving. No one edited the trigger. What is the most likely explanation the team should investigate first?
• One reusable pipeline runs a Notebook activity that processes digitised-object metadata for whichever branch is specified, but the underlying PySpark code inside the notebook needs to know which branch it's working on for that run. The pipeline already has a branch-code value available as a pipeline parameter. How should that value reach the notebook's code?
• A pipeline's reformatting notebook is set to run with a dependency condition of Completed on the upstream Copy activity, rather than Succeeded. The team notices the notebook still runs and produces garbage output even on nights when the Copy activity clearly failed. What should be changed?
• The archives network's master nightly pipeline needs to run a nearly identical loan-tracking sequence for each of several regional hubs, and each hub's sequence is already built and maintained as its own separate, well-tested pipeline. Rather than rebuilding that logic inside the master pipeline, what activity lets the master pipeline call each existing hub pipeline as a step?
• Two competing options are on the table for a new nightly ingestion step against the ticketing SaaS system: a curator-maintained Dataflow Gen2, or a PySpark notebook written and owned by the data engineering team. Governance policy says citizen-developer-maintained logic must stay in low-code tools that non-engineers can actually read and edit. Given that policy, which factor should decide between the two?
• A nightly digitisation-ingestion pipeline and a separate conservation-alert notebook are each scheduled independently, the alert notebook set to start thirty minutes after the ingestion pipeline's usual finish time. On nights the ingestion pipeline runs unusually long, the alert notebook still starts on its own fixed schedule and processes stale, incomplete data. What change fixes this properly?
• A data engineer is designing the full nightly digitisation-ingestion pipeline from scratch: a Copy activity should retry a few times on transient network blips, a reformatting notebook should run only once the copy genuinely succeeds, and a Teams alert should fire only if the copy ultimately fails after its retries are exhausted. What combination of orchestration features achieves all three requirements together?