Repair copied snapshots, source queries and Delta framing
A hands-on PL-300 lab. You produce the real artefact and 10 automated checks verify it behaves the way the exam expects.
Try this labAll PL-300 practice
- Certification
- PL-300
- Format
- Structured configuration
- Difficulty
- hard
- Estimated time
- 40 min
- Automated checks
- 10
The brief
Edit refresh.storage.json. tables maps the supplied table IDs to source, mode import/directquery/directlake, credential, gateway (or null), refreshTimes and framePolicy manual/automatic. Sources, credentials, gateways, commits and queries are read-only. Import refreshTimes copies the latest whole source version at each successful event; failed events preserve the earlier copy. An Import query reads that copy even while the source is offline. SQL DirectQuery reads the source at each query and therefore exposes outages; refreshTimes do not load an Import copy for it. Direct Lake is supported only for the OneLake Delta source, and queries use its last successful frame. Manual refreshTimes frame explicit versions; automatic framePolicy reacts to supplied commit events synchronously in this teaching timeline, with no native latency claim. SQL access requires an exact matching gateway endpoint, availability and nonexpired source-permitted credentials. Delta access needs its permitted credential. Keep original source bindings and complete row/filter identities, including signed, zero, null and absent results. Use either scheduled lake frames before required queries or automatic commit framing. Fit the eighteen-row Import copy budget; diagnostic result copies are excluded. Inspect failed-event and query-version receipts, repair without Reset and retain the source-outage error instead of inventing cached current data.
What the checks verify
Your work is graded on 10 independent properties, not on matching one reference answer.
- Compile supplied table/source bindings, modes, connection references and bounded update events.
- The historical Import copy remains queryable during the original SQL source outage.
- Historical queries use the initial and subsequently refreshed source versions.
- Current-table queries read the source versions available at their own query times.
- An unavailable current source produces its explicit outage error and no invented cached rows.
- Lake queries advance through the three committed Delta versions after successful framing.
- Selected historical and current queries return their own exact source observation identities.
- Lake zero, null and absent-member queries retain their distinct identities and latest framed version.
- Successful Import operations copy at most eighteen rows in the supplied local ledger.
- Changed signed values and source observation identities preserve the correct query-time versions and results.
Where this sits in the PL-300 blueprint
- Domain
- Manage and Secure Power BI
- Objective
- Create and Manage Workspaces and Assets
- Skill
- Gateways and Scheduled Refresh
Part of PL-300 preparation
Labs are written by ExamNova to teach the decisions the exam tests. They are not reproductions of vendor lab content.