10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.
Timed mock exam
40 questions in 48 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.
Prices are in US dollars, plus tax where it applies. Stripe, our payment processor, calculates tax at checkout.
All sales are final. If something is really wrong, such as a duplicate charge or a purchase that does not unlock what you bought, write to support@careerexampro.com and we will put it right.
One-time payment. Nothing renews.
You have an exam ticket for this practice test. Start the timed mock exam to use it.
How does a Spark reader determine the active Parquet data files for the latest snapshot?
It replays every JSON commit sequentially from 00000000000000000000.json through 00000000000000000025.json, ignoring the checkpoint files during normal reads.
It reads 00000000000000000020.checkpoint.parquet and applies only commits 21 through 25 on top of that state.
It scans all Parquet files in the table root directory directly and uses file modification timestamps to filter out uncommitted writes.
It acquires a distributed write lock on _delta_log/ and merges commits 21 through 25 into a temporary checkpoint before reading.
Show the answer
B. It reads 00000000000000000020.checkpoint.parquet and applies only commits 21 through 25 on top of that state.
Delta Lake checkpoints aggregate the table state up to a commit version in Parquet format. Readers load the latest checkpoint (version 20) and replay only subsequent JSON commits (21–25), enabling fast snapshot isolation without replaying the full log or locking readers.
Reference: Databricks Delta Lake Transaction Log (_delta_log) & Checkpoints
In ServiceNow, incident, problem, and change_request all extend the base task table. An administrator needs the inherited short_description field to have a custom default value and read-only behavior strictly on incident records without affecting problem or change_request. What is the recommended approach?
Edit the short_description Dictionary Entry directly on task, because child tables automatically isolate dictionary edits from siblings.
Create a duplicate custom column named u_short_description on incident and deactivate the inherited task.short_description field.
Configure a Dictionary Override on task.short_description scoped specifically to the incident table.
Modify the task table's extends attribute so incident becomes a standalone base table with independent column definitions.
Show the answer
C. Configure a Dictionary Override on task.short_description scoped specifically to the incident table.
A Dictionary Override lets an administrator customize inherited field attributes (such as default value, mandatory, read-only, or reference qualifier) for a specific child table (incident) without altering the parent task table or sibling tables like problem and change_request.
A data engineering team is designing a Medallion lakehouse pipeline for high-volume clickstream and order events. Where should deduplication, null-handling, schema conformance, and joining orders with customer dimensions happen before BI dashboards query daily revenue aggregates?
In the Bronze layer, so raw ingestion tables stay pre-aggregated and immutable source payloads do not consume cloud object storage.
In the Gold layer directly from raw files, skipping intermediate storage layers to avoid duplicating Parquet files across schemas.
In the Silver layer, keeping Bronze as raw append-only history and reserving Gold for business-level aggregates.
Inside the BI tool's semantic cache, while Bronze and Silver both store unparsed JSON strings partitioned by ingestion minute.
Show the answer
C. In the Silver layer, keeping Bronze as raw append-only history and reserving Gold for business-level aggregates.
In Medallion architecture, Bronze preserves raw, append-only ingestion history for replayability and audit; Silver holds cleansed, deduplicated, conformed datasets; and Gold exposes business-level aggregates and marts optimized for BI and ML consumption.
A ServiceNow team requires resolution_notes to be mandatory whenever an Incident's state is set to Resolved—whether updated via the browser form, a List Edit, an Import Set, or the Table REST API. Which configuration enforces this across every channel?
A UI Policy with Run scripts enabled, because ServiceNow automatically executes form UI Policies inside the REST API layer.
An onChange Client Script calling g_form.setMandatory('resolution_notes', true), because Client Scripts block server-side API writes.
A display Business Rule checking current.state == 6, because display rules validate incoming Import Set payloads before insert.
A Data Policy with Use as UI Policy on client enabled, enforcing the rule server-side on API/imports and client-side on forms.
Show the answer
D. A Data Policy with Use as UI Policy on client enabled, enforcing the rule server-side on API/imports and client-side on forms.
UI Policies and Client Scripts run only in the user's browser form and are bypassed by REST API calls, Import Sets, and standard list edits. A Data Policy enforces mandatory and read-only rules on the server across all entry points and can optionally mirror as a UI Policy on forms.
Reference: ServiceNow UI Policy vs. Client Script vs. Data Policy
An engineer overrides the Delta retention safety check and runs the following SQL on a frequently updated table:
SQL
SET spark.databricks.delta.retentionDurationCheck.enabled = false;
VACUUM prod.sales.orders RETAIN 48 HOURS;
What happens if an analyst subsequently runs SELECT * FROM prod.sales.orders TIMESTAMP AS OF current_timestamp() - INTERVAL 5 DAYS;?
It succeeds because VACUUM only deletes JSON commit files from _delta_log/ while keeping underlying Parquet files for 30 days.
It succeeds by automatically reconstructing the 5-day-old snapshot from Delta Lake's built-in 7-day Fail-safe archive.
It returns an empty result set with a warning because Delta Lake silently skips Parquet files removed by VACUUM.
It fails because VACUUM removed unreferenced Parquet files older than 48 hours, breaking Time Travel beyond that window.
Show the answer
D. It fails because VACUUM removed unreferenced Parquet files older than 48 hours, breaking Time Travel beyond that window.
Delta Lake's default VACUUM retention is 7 days (168 hours). Lowering retention to 48 hours permanently deletes unreferenced Parquet data files older than 48 hours; querying a 5-day-old version then fails with a missing-file error even if log metadata still exists.
Reference: Databricks Delta Lake VACUUM Retention & Time Travel