DP-700 practice questions
Microsoft · DP-700 · 200 questions
Original practice questions for the Microsoft Certified: Fabric Data Engineer Associate (DP-700) exam, covering implementing and managing an analytics solution (workspace settings, lifecycle management, security and governance, orchestration), ingesting and transforming data (loading patterns, batch and streaming ingestion/transformation across Lakehouse, Warehouse, Eventhouse/KQL, Dataflows Gen2, notebooks, pipelines, Eventstream, and OneLake shortcuts), and monitoring and optimizing an analytics solution — framed inside a national museum and archives network managing digitised collections, conservation telemetry, visitor-flow data, inter-branch loan tracking, and oral-history transcripts.
This course contains the use of artificial intelligence.
About the DP-700 exam
- Time allowed
- 1 hour 40 minutes
- Passing score
- 700 (scale 1-1000)
- Languages
- English, Japanese, Chinese (Simplified), German, French, Spanish, Portuguese (Brazil)
- Format
- Proctored, scheduled through Pearson VUE; may include interactive components
Schedule this exam The certification this earns
Exam details published by the vendor, checked 26 August 2026. Vendors change fees and formats without notice — confirm on the vendor's own page before you book.
Practice Quizzes
Test your knowledge with standard 20-question practice sets.
Quiz 1
Quiz 2
Quiz 3
Quiz 4
Quiz 5
Quiz 6
Quiz 7
Quiz 8
Quiz 9
Quiz 10
Browse by Domain
Study specific topics at your own pace.
Implement and manage an analytics solution · 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?
Ingest and transform data · 67 questions
- A national archives network loads the previous day's ticketing transactions from each branch's point-of-sale system into a Fabric Warehouse every night. The source system cannot reliably flag which rows changed, but the full table is small and inexpensive to pull each run. Which loading pattern best fits this scenario?
- An archives network's collection-management system stamps every catalogue record with a reliable LastModifiedUtc column whenever a record is re-described or corrected. The catalogue holds millions of records, but only a small fraction change on any given day. Which loading pattern is the best fit for refreshing the Lakehouse copy?
- Conservation sensors in a museum's rare-manuscripts vault emit humidity, light, and vibration readings continuously, and curators want alerts within seconds of an out-of-range reading. Which loading pattern fits this requirement?
- A data engineer is preparing cleansed loan-tracking data for a dimensional model that will report on objects loaned between museum branches. Each branch dimension row will be joined into the loan fact table, and branch names occasionally get renamed after reorganizations. Which practice should the engineer follow when preparing the branch dimension for loading?
- An archives team is ingesting scanned document images and their OCR text output for oral-history transcripts. The files vary in format, some processing will use PySpark notebooks, and there is no requirement for T-SQL querying against this data yet. Which Fabric data store should the team choose to land this data?
- A museum network's finance team needs to run complex T-SQL joins and aggregations across ticketing revenue and membership billing data, and several analysts are only comfortable writing SQL, not Spark code. Which Fabric data store best matches this need?
- Vibration and light sensors across a museum network's storage vaults emit millions of timestamped readings per day, and conservation staff need fast time-series queries filtering by branch, sensor type, and time window. Which Fabric data store is designed for this workload?
- A national archives network is designing a medallion architecture in its Lakehouse for digitised-collection metadata pulled nightly from each branch's collection-management system. What should the bronze layer contain?
- Continuing the archives network's medallion design, the team wants a layer where branch-specific field names are standardized, duplicate loan records across systems are removed, and data types are validated before anything is aggregated for reporting. Which layer is this?
- The archives network's leadership wants a single table showing total visitor counts per branch per month, ready to plug directly into a Power BI dashboard with no further joins or cleansing needed by the report author. Which medallion layer should produce this table?
- A regional branch of the archives network keeps its own digitised-object files in an existing Azure Data Lake Storage account that it cannot migrate. The central data engineering team wants to reference those files from the central Lakehouse without duplicating the storage or building a copy pipeline. Which OneLake capability should they use?
- The archives network's membership system runs on an operational Azure SQL Database, and the analytics team wants a near-real-time, continuously refreshed copy of its tables in OneLake without hand-building an ingestion pipeline. Which capability is designed for this?
- An archives network needs to combine an oral-history transcript dataset with heavy PySpark transformations that write large new derived tables, and the result must be physically stored inside the destination Lakehouse rather than left dependent on the original source location. Why would a pipeline copy be favored here over a OneLake shortcut?
- A data engineer sets up mirroring against the archives network's donor-management database so its tables appear in OneLake for analytics. Which statement correctly describes what mirroring provides once it is configured?
- A data engineer designing the archives network's nightly ingestion wants to isolate any failure in a branch's export format so a bad file cannot corrupt the conformed silver tables, and wants the ability to reprocess a failed run without re-extracting from the source branch system. Which practice addresses this?
- A catalogue record's artifact-condition classification is corrected from a data-entry typo. Analysts agree there is no reporting value in keeping a record of the incorrect classification once it's fixed, and the dimension row should simply reflect the current, correct value. Which slowly changing dimension approach fits this correction?
- An archive's catalogue record for a manuscript is re-described over time as scholarship advances: its subject classification changes twice over several years, and curators want reports to be able to show which classification was in effect at the time each past loan or exhibit occurred. Which slowly changing dimension approach supports this?
- A branch dimension tracks the administrative region a branch reports to. Leadership only ever needs to compare a branch's current region against its immediately prior region for a single transition review, and they explicitly do not need full multi-version history. Which slowly changing dimension design fits this narrow requirement most efficiently?
- A team preparing a dimensional model for inter-branch loan reporting has not yet decided what a single row in the loan fact table represents: some want one row per loan agreement, others want one row per day an object remains on loan. Which step should the team complete before building the fact table?
- A team implementing a Type 2 slowly changing dimension for museum branches needs the loan fact table to always join to the exact version of a branch's attributes that was current when each loan occurred. What must the fact table reference to make this work correctly?
- A gallery's visitor-flow sensors stream footfall counts continuously, and the reporting requirement is a rolling five-minute total per gallery, refreshed as new events arrive rather than recomputed from all history each time. Which loading pattern characteristic should the design center on?
- A loan-tracking fact row arrives referencing a newly acquired object that has not yet been fully catalogued, so no matching row exists in the object dimension. Rejecting the fact would delay reporting on the loan until cataloguing finishes days later. Which loading pattern handles this kind of late-arriving dimension gap?
- An archives network is choosing where to land newly digitised oral-history audio files alongside the semi-structured JSON metadata each file's OCR and transcription process produces, before any Spark transformation happens. Which factor should most directly drive the data store choice at this stage?
- A national archives network is standing up a home for newly digitised object metadata coming from a dozen branches. Each branch's export carries a slightly different set of fields, the volume will grow into the tens of millions of records, and the conservation team wants to run PySpark notebooks directly against the data alongside ad-hoc SQL queries. Which Fabric data store best fits this requirement?
- A museum's conservation team streams humidity, light, and vibration readings from gallery and vault sensors around the clock, generating hundreds of thousands of readings per hour. Analysts need to run fast time-series queries, like the average vault humidity over the last six hours, against this telemetry. Which Fabric data store is purpose-built for this workload?
- The archives network's finance office keeps ticketing revenue and membership-fee data that must support multi-table transactions, foreign-key style relationships between branches and transactions, and heavy T-SQL reporting for the annual audit. Which Fabric data store should host this data?
- A collections registrar with no coding background needs to clean up an inconsistent branch export of inter-branch loan records — trimming whitespace, renaming a couple of columns, and filtering out cancelled loans — before it lands in a Lakehouse table. Which tool is the best fit for this task?
- A data engineer needs to run a custom deduplication and text-normalization routine across millions of OCR-extracted oral-history transcript records, using a third-party Python NLP library and iterative logic that doesn't map cleanly onto point-and-click transformations. Which tool should the engineer use?
- An analyst already has gallery sensor readings landed in an Eventhouse and wants to quickly check, ad hoc, which vault exceeded a vibration threshold in the last hour before deciding whether to escalate. Which tool should the analyst reach for first?
- A regional branch keeps its own scanned-document archive in an Azure Data Lake Storage Gen2 account that predates the museum network's move to Fabric. The central data engineering team wants to query and transform that data through OneLake without physically copying it into a Lakehouse. What should they create?
- Two workspaces in the same Fabric tenant each host a Lakehouse. The exhibits team's workspace needs read access to the digitised-object Delta table that lives in the collections team's Lakehouse, without maintaining a second physical copy of that multi-terabyte table. What is the appropriate solution?
- The archives network's donor-relationship data lives in an operational Azure SQL Database used by the development office, and analysts want that data reflected in OneLake as near-real-time, read-only Delta tables without the team building and maintaining a custom extraction pipeline. Which Fabric capability directly fits this need?
- After enabling mirroring for the development office's Azure SQL Database, an analyst opens the mirrored tables in OneLake and tries to run an UPDATE statement to correct a donor's mailing address directly against the mirrored table. What should the analyst expect?
- Every night, the archives network needs to pull the previous day's visitor-flow CSV exports from each branch's on-premises file server into a Lakehouse's Files section before any transformation happens. Which Fabric orchestration capability is designed to move this raw data into Fabric?
- A data engineer is building a pipeline that must first copy freshly digitised object images into a Lakehouse, and then run a complex PySpark cleanup routine — including a third-party image-metadata library — against those files as the next orchestrated step. Which pipeline activity should invoke that PySpark cleanup step?
- A branch's ticketing point-of-sale system occasionally re-sends the same transaction record after a network retry, so a Lakehouse table built from a PySpark notebook ends up with exact duplicate rows sharing the same transaction ID. Which PySpark approach removes those duplicates before the data is written downstream?
- A nightly batch adds new inter-branch loan records to a Warehouse table, but some records represent updates to loans that were already loaded the previous night — for example, a loan's return date being filled in late. A straight INSERT would create duplicate rows for those loans. Which T-SQL approach correctly applies both new and updated records in a single operation?
- Conservation telemetry lands in an Eventhouse as raw sensor rows with separate temperature-in-Celsius and humidity-percentage fields. Before the data is queried by the visualization team, an engineer wants to compute and store a derived risk-score column on each row as it's processed. Which KQL capability is designed for adding a computed column like this?
- A reporting team wants a single, wide table that combines each digitised object's core catalogue record with its branch name, its current conservation status, and its most recent loan destination — all of which currently live in four separate normalized tables joined by keys. Repeated joins across these tables are slowing down the team's dashboards. What transformation should a data engineer apply to address this?
- A junior data engineer objects to denormalizing the object-catalogue reporting table, arguing that duplicating branch names and conservation-status text across millions of rows wastes storage and risks inconsistency if a branch is ever renamed. A senior engineer defends the design anyway. What is the strongest justification for choosing denormalization here despite that trade-off?
- A data engineer has a Lakehouse table of individual ticket scans and needs to produce, via a PySpark notebook, a daily total visitor count per branch for a dashboard. Which PySpark pattern correctly produces one row per branch per day with a summed count?
- An analyst needs a T-SQL query against a Warehouse table of inter-branch loan records that reports only the branches that have sent out more than 20 loans this year, along with each qualifying branch's total loan count. Which clause is required, in addition to GROUP BY, to filter on the aggregated count itself?
- A branch's handheld scanner occasionally uploads the same ticket-scan event twice after a connectivity drop, and a data engineer needs to remove these exact-duplicate rows from a Warehouse table using T-SQL rather than PySpark. Which T-SQL pattern correctly identifies and removes the duplicates while keeping exactly one copy of each?
- An oral-history ingestion job normally appends each interview transcript's metadata to a Lakehouse table the same day it's recorded, but a batch of transcripts from a rural branch arrives three weeks late because of a slow network connection, and some of those late records are corrections to transcripts that were already partially loaded earlier. Which approach correctly handles this late-arriving, partly-overlapping data?
- A dozen regional branches each export their collection-management catalogue on a different schedule and periodically add a new field — one branch recently started including a 'conditiongrade' column that no other branch has yet. A nightly load process ingesting these exports into a Lakehouse table needs to keep working without manual schema edits every time a branch changes its export. What should the ingestion approach do to handle this?
- The conservation team at a national museum and archives network wants to take a live stream of gallery humidity readings and fan it out to three destinations at once — a Lakehouse table for long-term archiving, a Data Activator for threshold alerts, and a Power BI report — applying only light filtering along the way, with no custom code. Which Fabric capability best fits this need?
- A data engineer is building an Eventstream that ingests turnstile tap events from every branch of a national museum network and needs to compute a rolling count of visitors per gallery every five minutes before landing the results in an Eventhouse. Which Eventstream capability should the engineer use to do this without leaving the no-code canvas?
- A PySpark notebook uses Spark structured streaming to compute a five-minute tumbling window count of oral-history recording-upload events from branch archives, but a network outage occasionally delays some upload-confirmation events by up to twenty minutes. Which technique should the engineer add to the streaming query so those delayed events can still be incorporated into the correct window without the state store growing indefinitely?
- Vibration-sensor readings from a museum's vault racking arrive at an Eventhouse table with an explicit event-time column, but network buffering means the rows are not always ingested in the same order the sensors generated them. An analyst writing a KQL query needs results grouped strictly by when each vibration actually occurred, not by when the row reached the Eventhouse. Which approach should the analyst take?
- An Eventstream aggregates turnstile-tap events into a visitor count for each museum branch, and the requirement is that every tap belongs to exactly one, non-overlapping ten-minute reporting bucket with no gaps and no double-counting across buckets. Which windowing function satisfies this requirement?
- A conservation dashboard needs to show a smoothed, frequently-updating view of a gallery's average lux exposure, refreshing every minute over a rolling five-minute span so curators can spot a creeping light-exposure trend without the choppiness of a strict five-minute tumbling average. Which windowing function fits this need?
- Security wants an immediate alert the instant three or more vault-vibration events occur within any three-minute span, evaluated continuously as each new reading arrives rather than only at fixed checkpoints. Which windowing function is designed for this kind of continuous, event-triggered evaluation?
- Analysts want to measure how long each visitor lingers inside a single gallery by grouping that visitor's motion-sensor pings together whenever consecutive pings are no more than two minutes apart, and starting a new group whenever a gap of more than two minutes occurs. Which windowing function models this directly?
- A building-management system emits temperature, humidity, and CO2 readings from a gallery's HVAC controller, and all three values for a given moment always carry the exact same timestamp because they are sampled together. An engineer wants to group and combine those three simultaneous readings into a single row per timestamp, without introducing any time-span logic. Which windowing function matches this need?
- A Spark structured streaming job aggregates loan-tracking scan events (an object moving between branches) into five-minute tumbling windows with a ten-minute watermark. A scan event with an event-time timestamp that is fifteen minutes older than the current watermark then arrives. What happens to that event?
- Donor oral-history upload-confirmation events sometimes arrive at an Eventstream out of the order in which they actually occurred, because branches upload over inconsistent network links. The downstream Eventhouse table needs to reflect correct chronological order for time-based analysis regardless of arrival order. What is the correct way to address this?
- Curators want to run ad hoc, exploratory queries over months of historical gallery-temperature telemetry — comparing trends across seasons, finding anomalies, and slicing by branch — using a query language built for fast time-series analytics at scale, rather than building a fixed routing topology. Which Fabric engine is purpose-built for this kind of analysis?
- An engineer needs to join a live stream of building-management HVAC events with a live stream of gallery-occupancy events, computing a rolling correlation between occupancy and temperature drift using custom stateful logic that goes beyond simple filtering or aggregation. Which tool should the engineer reach for?
- A Spark structured streaming job aggregates artifact-scan events into five-minute tumbling windows and writes results to a Lakehouse table using append output mode. The team notices that windows only appear in the output table well after they close, and never get corrected once written. Which streaming concept explains this behavior?
- A partner museum exposes its object-loan catalogue as a paginated JSON REST API rather than a database or file export, and the archives network wants to pull the full catalogue into a Lakehouse table every night, with authentication handled through a stored connection and pagination handled automatically, without anyone writing custom code. Which Fabric capability directly fits this need?
- A branch-transfer telemetry stream logs each time a crated artifact passes a loading-dock scanner during an inter-branch loan move. The reporting requirement is a strict, non-overlapping count of scans per fifteen-minute block for the whole day, where each scan counts toward one and only one block. Which windowing function is the correct fit?
- Facilities wants a congestion indicator for the main atrium that updates every two minutes but reflects the average visitor-flow rate over the trailing ten minutes, so a short burst at the entrance doesn't cause the indicator to spike and immediately drop back down. Which windowing function delivers this trailing, overlapping average?
- A conservation Data Activator needs to evaluate, the instant each new gallery-temperature reading arrives, whether the average temperature over the trailing four minutes has crossed a damage-risk threshold, so the alert can fire on the very reading that pushes it over rather than waiting for a scheduled check. Which windowing function is designed to re-evaluate on every incoming event like this?
- An archivist reviewing oral-history recording sessions wants each interview segment automatically grouped by continuous speech, where consecutive audio-activity events belong to the same segment as long as no silence gap longer than ninety seconds occurs, and a new silence gap longer than that starts a new segment. Which windowing function models this behavior?
- A gallery's environmental controller emits a single combined reading of temperature, humidity, and lux for a given instant, and all three values in that reading always share one identical timestamp because they come from the same sampling cycle. Reporting needs one output row per sampling instant that carries all three values together, with no time-span logic involved. Which windowing function is the direct match?
- A branch occasionally uploads inter-branch loan-scan events up to two hours late due to intermittent connectivity at remote sites, far longer than what a real-time Spark structured streaming watermark can reasonably tolerate without ballooning state. Which pattern should the team adopt to still capture these very late scans without keeping years of streaming state open?
- A facilities team wants building-management fire-suppression-system heartbeat events routed continuously to both an Eventhouse for historical KQL analysis and a Data Activator that pages on-call staff if a heartbeat is missing for more than two minutes, with light field renaming along the way and no team member available who can write Spark code. Which Fabric engine should this team choose?
Monitor and optimize an analytics solution · 66 questions
- A regional archives supervisor wants a single place each morning to check the status of last night's digitization pipeline runs, Dataflow Gen2 refreshes, and notebook jobs across every branch workspace before opening the reading room. Which Fabric monitoring surface should they check first?
- The overnight digitization pipeline for a museum branch has started finishing later each week, and gallery staff need it done before the doors open. Which Fabric monitoring view lets an engineer see how long each activity inside that pipeline run took, so the slow stage can be identified?
- A conservation team wants to be notified automatically if the humidity-sensor stream from a rare-manuscripts vault stops sending readings for more than 15 minutes, without anyone having to watch a dashboard. Which Fabric capability is purpose-built for defining this kind of condition-and-action rule against live data?
- An engineer suspects that a gallery's vibration-sensor Eventstream has stopped receiving events, but no alert has fired yet. Which built-in Eventstream capability lets them confirm, visually, whether data is currently flowing through the stream?
- A data engineer's PySpark notebook that cleans OCR output from digitized oral-history transcripts has been running far longer than usual overnight. Which Fabric monitoring surface lets them inspect the notebook's Spark application, including its stages and executors, to see where time is being spent?
- A Dataflow Gen2 that denormalizes and cleans loan-tracking records from branch collection-management systems runs nightly, and the team wants to see whether recent runs succeeded and how long each one took, without opening the Dataflow's editor. Where should they look?
- A branch's ticketing semantic model refreshes nightly so morning attendance dashboards are current, but stakeholders report that yesterday's numbers looked stale. Which monitoring step should the team take first to determine whether the scheduled refresh actually ran and succeeded?
- Leadership wants to be notified by email the moment the nightly ticketing semantic model refresh fails, rather than discovering it the next morning when the dashboard looks wrong. Which approach lets them configure that kind of automatic, condition-based notification?
- With dozens of branch workspaces each running their own nightly pipelines, dataflows, and notebooks, an operations lead wants to quickly narrow the Monitoring hub down to only the runs that failed in the last 24 hours across every workspace they can access. Which capability of the Monitoring hub supports this?
- A conservation team ingests vault humidity and light readings into an Eventhouse continuously, and they want to check whether any recent batches of telemetry failed to ingest into the KQL database, rather than waiting for a downstream query to come up short. Where does this kind of ingestion status information live?
- The overnight digitization pipeline across several branches has recently started running slower, and an engineer suspects the shared Fabric capacity is being throttled by another heavy workload rather than the pipeline itself having gotten worse. Which monitoring tool should they check to confirm whether capacity throttling is occurring?
- A workspace admin is setting up automated monitoring so that if a branch's visitor-count Eventstream reports a value above a defined threshold, a Teams message is sent to the operations channel automatically. Conceptually, what two things must be defined together for this to work in Data Activator?
- During a busy exhibit-opening week, an engineer checking the Monitoring hub notices that a branch's nightly ingestion pipeline has been showing "In Progress" for far longer than its usual runtime. Which monitoring action lets them confirm which specific activity inside that run is still executing, before deciding whether to investigate further?
- An engineer reviewing a Spark application for last night's OCR-cleanup notebook run notices one stage took ten times longer than every other stage. Which monitoring detail inside that Spark application view would help them see whether the slow stage was caused by uneven data distribution across tasks?
- A team wants an automatic alert if a branch's gallery-temperature Eventstream reports a reading outside the safe conservation range for more than five minutes continuously, not just a single spike. Which Data Activator concept lets them require the condition to hold for a sustained period before triggering?
- Reviewing several weeks of a branch's ticketing semantic model refresh history, an analyst notices the refresh duration has been climbing steadily even though the schedule hasn't changed. What does monitoring this trend, rather than only the most recent run, make visible that a single run's status would not?
- An engineer needs to decide whether to check the Monitoring hub or a specific Dataflow Gen2's own refresh history to answer the question "did every scheduled dataflow refresh across all our branch workspaces succeed last night?" Which is the better starting point, and why?
- A branch's Dataflow Gen2 that ingests loan-tracking updates is scheduled to run once nightly, but the refresh history shows two runs starting within the same hour on several recent nights. Which monitoring habit would have surfaced this pattern earliest?
- A team wants an automatic notification whenever the daily visitor count ingested from ticketing scanners into an Eventhouse exceeds a set number, so operations can plan extra staffing. Which piece of information must be defined for a Data Activator rule to act on this specific numeric value?
- An analyst monitoring a branch's semantic model refresh history notices refreshes have grown long enough that they sometimes are still running when the museum opens and dashboards are first viewed. What does this observation, drawn purely from monitoring the refresh history, indicate the team should evaluate?
- A workspace admin has defined a Data Activator condition for a failed nightly pipeline, but wants the resulting alert to reach the operations team's Teams channel rather than a single person's inbox. What must be configured on the alert's action for this to work?
- Before galleries open each morning, an operations lead wants one habitual check that covers pipeline runs, dataflow refreshes, and notebook jobs across every branch, catching anything that failed or is still stuck running overnight, without relying on any single item's individual alert having been configured. Which practice best satisfies this?
- A branch's collection-management system starts exporting its nightly catalogue extract with two columns swapped after an unannounced vendor update, and the archive network's pipeline Copy activity maps source columns to the warehouse table by position. The next morning the pipeline run shows a green succeeded status, but curators report accession numbers landing in the condition-notes field. What should the engineer check first to confirm this is the root cause?
- A pipeline uses a ForEach activity to loop over every branch's inter-branch loan-tracking feed and load it into a Lakehouse table. Overnight the whole pipeline run fails, and the engineer needs to find which specific branch's iteration caused the failure and why. Where should they look?
- A pipeline's Notebook activity, which runs a PySpark notebook that cleans OCR text from scanned oral-history transcripts, fails. The pipeline's own run history simply shows the activity as failed with a generic message that the notebook run did not complete successfully. What should the engineer do to find the actual root cause?
- A nightly pipeline loads digitized artifact images into a Lakehouse and then runs two downstream activities that generate thumbnails from those images. One night the image-copy activity fails, and in the pipeline's monitoring canvas the two thumbnail activities appear grayed out instead of red. How should the engineer interpret this?
- A branch renames a column in the spreadsheet it uses to track object loans between museum branches, and the following night a Dataflow Gen2 that consumes that spreadsheet fails to refresh. Where should the engineer look to identify which query step broke and why?
- A Dataflow Gen2 transforms nightly visitor-ticket counts from a branch's kiosk export, converting a text column to a whole-number type. The refresh itself completes, but several rows now show error values in that column instead of numbers, because a few kiosks exported stray characters alongside the digits. What is the best way to identify exactly which source rows are causing this?
- A Dataflow Gen2 that pulls a legacy card-catalog database, reachable only through an on-premises data gateway at one regional branch, fails to refresh three nights out of five, with no changes to the query logic. On the nights it fails, the refresh history shows the failure occurring almost immediately, before any transformation step begins. What does this pattern most strongly suggest?
- A Dataflow Gen2 merges a digitized-object metadata query with a conservation-status query using a shared object ID, joining them to enrich each object's record. After a source system change, the merge step starts returning zero matches instead of the expected joined rows, even though both tables clearly still contain matching IDs when viewed separately. What is the most likely cause?
- A PySpark notebook processes a large nightly batch of OCR text extracted from scanned oral-history transcripts. One cell calls .collect() to pull the entire distributed dataset into the driver for a quick inspection, and that cell now fails on especially large batches while earlier cells that only build and cache Spark DataFrames succeed. What does this pattern point to?
- A notebook's very first cell reads from a Lakehouse table that holds newly digitized artifact metadata, and it fails immediately, reporting that the table cannot be found, even though the engineer can see the table listed in the Lakehouse explorer. The notebook that is supposed to create this table each night runs later in the same pipeline, after this one. What is the most likely root cause?
- A notebook appends a nightly batch of newly digitized-object metadata to an existing Delta table in a Lakehouse. After the upstream extraction process starts including a new provenance field, the append fails with an error indicating the incoming data's schema does not match the target table. What is happening?
- One morning a scheduled notebook fails and its run detail shows no cells executed at all; the failure occurred while the notebook was still trying to attach to a Spark session. On other mornings the same notebook runs a specific cell that then errors out partway through processing. How should an engineer route these two different failures?
- An Eventstream carrying humidity and light readings from gallery conservation sensors feeds a table in an Eventhouse. After a branch upgrades its sensor firmware, the field names in the incoming JSON payload change slightly, and the Eventhouse's ingested row count drops sharply overnight even though the sensors are still transmitting. Where should the engineer look to confirm the cause?
- An analyst runs a KQL query against an Eventhouse table holding vibration sensor readings from a vault, filtering for the last five minutes, and gets back an unexpectedly empty result. The Eventhouse itself reports as healthy, and querying for the last hour instead returns plenty of rows, just none in the most recent few minutes. What is the most likely explanation?
- An Eventhouse has an update policy that runs a function to transform raw gallery sensor readings into a cleaned, derived table used for conservation dashboards. After the raw table's column names change, the derived table stops receiving new rows, while the raw table itself keeps filling normally. What has most likely happened?
- An Eventstream carries live ticket-scanner events from a museum branch's turnstiles through a filter step and into an Eventhouse destination. Visitors keep scanning tickets all afternoon, but the destination stops receiving any new events partway through the day. What is the best way to pinpoint where in the Eventstream the data flow actually stops?
- An Eventstream includes a filter step meant to drop test events generated by a branch's turnstile hardware during maintenance, keeping only real visitor scans. After the vendor updates the turnstile firmware and renames one of the fields the filter condition checks, the filter step's live preview shows every single event being dropped, including legitimate visitor scans. What has happened?
- An Eventstream's live preview shows visitor-flow events from a branch's people-counting sensors passing successfully through every node, including the final node right before the destination. Yet the target Eventhouse table shows no new rows arriving. What does this pattern suggest?
- A scheduled T-SQL stored procedure in a Fabric Warehouse aggregates nightly visitor-ticketing totals by pulling from a view that finance recently redefined, dropping a column the procedure references. The next run fails with an error naming that specific column as invalid. What should the engineer conclude?
- A T-SQL query against a Fabric Warehouse table of donor-gift records implicitly converts a text donation-amount column to a numeric type for a summary report. The query fails with a conversion error, and the engineer confirms the vast majority of rows convert without issue. What should the engineer check first?
- A T-SQL query that has run successfully for months against a Warehouse table of loan-tracking records suddenly fails, reporting that the object cannot be found, even though the table clearly still exists and other queries the same engineer runs work fine. After a recent reorganization, tables were moved into a new schema. What is the most likely explanation?
- An analyst's T-SQL query against a Warehouse table of exhibit loan agreements occasionally times out or fails with a concurrency-related error, but only during the narrow window each night when a pipeline is bulk-loading new loan records into that same table. Running the identical query at any other time of day works without issue. What should the engineer conclude?
- A national archive's Lakehouse stores humidity, light, and vibration telemetry streamed from conservation sensors in ten vault rooms, with each sensor writing a new file every few seconds. Curators notice that queries against the sensor table have grown steadily slower even though the table's total row count is only growing at a steady, predictable rate. What is the most likely cause?
- A digitisation team writes millions of rows of scanned-document metadata into a Fabric Lakehouse table using Spark, and the table is later queried heavily through both Power BI reports and the SQL analytics endpoint. Which optimization, applied automatically when the Spark job writes the table, is specifically intended to speed up exactly this kind of downstream read?
- A museum network's Lakehouse holds a decade of visitor-flow and ticketing history across dozens of branches. Analysts almost always filter their reports to a single month or a single quarter, yet every query currently scans the full ten years of files before applying that filter. Which change to the table's physical layout would most directly reduce the amount of data scanned for these queries?
- A data engineer runs table-compaction (OPTIMIZE) on a large digitised-artifact metadata table every night, and the underlying storage size keeps growing even though the number of active files stays roughly the same after each run. What is the most likely reason, and what should the engineer do next?
- To speed up queries, an engineer partitions a branch loan-tracking table by branch code, loan date, and exact loan time, resulting in thousands of partitions each holding only a handful of rows. Query performance gets worse, not better, after this change. What is the most likely explanation?
- A nightly pipeline loads collection updates from twelve independent regional branch archives into a central Lakehouse using a single ForEach activity that processes branches one at a time. The pipeline finishes correctly every night but now runs long enough to delay the morning reporting refresh. The branches have no dependency on each other. What change would most directly reduce the pipeline's total run time?
- A pipeline currently uses a Dataflow Gen2 to move a straightforward, unmodified extract of daily exhibit-ticket sales from a source database into a Warehouse staging table — no transformation logic is applied at any step. The load is one of the slowest steps in the nightly schedule. What change is most likely to improve its performance, without changing what data ends up in the staging table?
- After a one-time bulk load adds several years of archived loan-tracking records into an existing Fabric Warehouse table, a T-SQL join query that used to return quickly now takes noticeably longer, even though no query text changed. What is the most likely fix?
- A T-SQL report against the Warehouse computes, for every branch, the number of loan requests that occurred after that branch's most recent inspection date, using a correlated subquery inside the SELECT list that re-evaluates the inspection lookup for every branch row. The query is one of the slowest in the nightly report suite. Which rewrite is most likely to improve its performance while returning the same results?
- Conservators run frequent KQL queries against an Eventhouse table holding vault humidity and vibration telemetry, almost always looking at the last 48 hours of readings, even though the table retains several years of history for compliance. Queries against the recent window are slower than conservators expect. Which Eventhouse setting is designed specifically to speed up queries like this?
- An Eventstream ingests motion and vibration events from gallery sensors across every branch. On ordinary days it keeps up comfortably, but during peak visitor events, when sensor event volume spikes sharply, downstream processing starts lagging noticeably behind real time. What change to the Eventstream is most directly aimed at handling this kind of throughput spike?
- A notebook that runs PySpark cleanup on OCR output from digitised oral-history transcripts is assigned a fixed-size Spark pool sized for the largest transcript batch the archive ever processes, even though most nightly batches are far smaller. Utilization metrics show the pool sitting mostly idle on typical nights, while capacity costs stay constantly high. What change addresses this most directly?
- A PySpark job joins a very large fact table of digitised-object records against a small lookup table of the network's dozen branch codes and names. The job spends most of its time shuffling the huge fact table across the cluster just to match it with a handful of lookup rows. Which technique is most directly aimed at eliminating that unnecessary shuffle?
- A notebook builds a cleaned DataFrame of oral-history transcript metadata through several PySpark transformation steps, then uses that same DataFrame as the input to three separate downstream aggregations. Spark re-executes the entire chain of upstream transformations from scratch for each of the three aggregations, tripling the total runtime. What change would most directly avoid that repeated recomputation?
- A PySpark job aggregates a modest-sized daily visitor-count dataset by branch and hour, but after the group-by-and-aggregate step, Spark produces thousands of tiny output partitions, most holding only a few rows, and the job spends more time on task scheduling overhead than on actual computation. What is the most likely cause?
- An engineer notices that a Lakehouse table of ticket-scan events, which suffers from the small-file problem after months of frequent streaming writes, is slow not only in Spark notebooks but also when analysts query it through the SQL analytics endpoint using plain T-SQL. Why does the same file-layout issue affect both engines?
- A dashboard repeatedly runs the same KQL summarize-and-aggregate query against a large, continuously-growing Eventhouse table of vibration-sensor readings to show a rolling hourly average per vault. Each dashboard refresh re-scans and re-aggregates the full underlying table, which is becoming slow as history accumulates. Which Eventhouse feature is designed to precompute and store this kind of recurring aggregation so refreshes don't have to reprocess raw data from scratch each time?
- An engineer who previously worked with Azure Synapse Analytics dedicated SQL pools wants to define a hash distribution key on a large Fabric Warehouse fact table to control how its rows are distributed across compute nodes, the way they used to in Synapse. What should they understand about doing this in a Fabric Warehouse?
- A nightly pipeline copies a very large volume of digitised-object metadata directly from an on-premises collection-management database into a Fabric Warehouse table using a single Copy activity, and the load consistently runs far longer than the volume alone seems to justify. What change is most likely to improve throughput for this kind of large direct load into a Warehouse?
- Rather than compacting small files after the fact with a scheduled OPTIMIZE job, an engineer wants Spark to avoid generating excessive small files in the first place when it writes results from a nightly transformation of loan-tracking records into a Lakehouse table. Which approach addresses the problem at write time rather than after the fact?
- Analysts frequently filter a large Lakehouse table of digitised-object records by object category, but the table isn't partitioned by category because category values change over time and partitioning by it would create excessive small partitions. Query performance on category-filtered searches is still poor despite the table being regularly compacted. Which additional compaction option would most directly help category-filtered queries skip irrelevant data without partitioning the table by category?
- A report queries a wide Lakehouse table of digitised-object metadata that has over a hundred columns, including large free-text conservation-note fields, but the report only ever needs five specific columns such as object ID, category, and current branch. The query currently uses SELECT and is notably slower than reports of similar row count that select only a few columns. What is the most direct explanation, and the most direct fix?
These questions are original practice material and are NOT actual exam questions or brain-dump content. All vendor marks are trademarks of their respective owners. This site is not affiliated with, endorsed by, or sponsored by the exam vendor.