Sample question 1
intermediateDomain 1, objective 2A team runs SQL-only ELT and BI queries on Databricks on AWS. Their network design keeps an event bus and several databases in their own cloud network, and queries must federate to an on-premises database over that network. The workspace is in a region that does not offer serverless SQL warehouses, and the team wants better than entry-level performance. Which SQL warehouse type fits best?
Choose one answer.
- Option A:
A serverless SQL warehouse.
- Option B:
A pro SQL warehouse.
- Option C:
A classic SQL warehouse.
- Option D:
A Lakehouse Real-Time SQL warehouse.
Show answer and explanation for sample question 1
Correct answer: B
Why
Serverless SQL warehouses are recommended when available. A pro SQL warehouse is the choice when serverless is not available in a region or when you need custom-defined networking for federation or hybrid setups, because its compute layer sits in your own cloud account. Classic warehouses give only entry-level performance.
Every option
- A(incorrect)
Incorrect. Serverless is the recommended type when it is available, but this region does not offer it. Its compute also runs in the Databricks account rather than in the team's own network.
- B(correct)
Correct. A pro SQL warehouse supports Photon and Predictive IO, and its compute layer is in your AWS account. It is the documented choice when serverless is not available in a region or when custom-defined networking is needed for federation or hybrid architectures.
- C(incorrect)
Incorrect. A classic warehouse also runs in your account but supports only Photon, so it gives entry-level performance. It is meant for basic interactive exploration when serverless or pro are not options.
- D(incorrect)
Incorrect. Lakehouse Real-Time is a serverless warehouse type, so it is not available in this region. It is also built for sub-second read queries and supports only SELECT and CREATE TABLE AS SELECT, which does not fit ELT.
Official documentation cited