The correct answer is that Hyperscale does not support cross-database queries or elastic queries, which is the key limitation to evaluate. This restriction stems from Hyperscale’s unique architecture, where compute nodes are stateless and storage is fully separated, preventing the engine from coordinating queries across multiple logical databases in a single statement. On the DP-300 exam, this concept tests your understanding of how service tier trade-offs affect real-world application design—especially when teams assume all features are available across tiers. A common trap is to overlook that Hyperscale excels at massive storage and rapid scaling but sacrifices multi-database query capabilities found in General Purpose or Business Critical tiers. Remember the memory tip: “Hyperscale scales up, not across”—if your app needs to join data from separate databases, Hyperscale is not the right fit.
DP-300 Plan and implement data platform resources Practice Question
This DP-300 practice question tests your understanding of plan and implement data platform resources. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your company is planning to deploy a new application that uses Azure SQL Database with a Hyperscale service tier. The application requires near-instantaneous scaling of compute resources without downtime. The database will handle large data volumes (over 10 TB). Additionally, the application team wants to use the latest database features, including JSON support and graph queries. Which considerations should you evaluate before choosing Hyperscale?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Hyperscale does not support cross-database queries or elastic queries.
Option D is correct because Azure SQL Database Hyperscale does not support cross-database queries or elastic queries. This limitation is critical for the application team if they need to query across multiple databases in a single query, which is a common requirement for distributed applications. The Hyperscale architecture separates compute from storage, making cross-database query capabilities unavailable, unlike other service tiers such as General Purpose or Business Critical.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Hyperscale does not support graph data features such as node and edge tables.
Why it's wrong here
Incorrect: Hyperscale supports graph features.
✗
Hyperscale does not support zone-redundant configuration for high availability.
Why it's wrong here
Incorrect: Hyperscale supports zone redundancy (preview).
✗
Hyperscale does not support JSON functions like JSON_VALUE and JSON_QUERY.
Why it's wrong here
Incorrect: Hyperscale supports all JSON functions.
✓
Hyperscale does not support cross-database queries or elastic queries.
Why this is correct
Correct: Hyperscale does not support cross-database queries or elastic query features.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Hyperscale supports all features of other tiers due to its advanced capabilities, but Microsoft specifically excludes cross-database and elastic queries in Hyperscale, making it a common oversight in exam questions.
Detailed technical explanation
How to think about this question
Hyperscale's architecture uses a distributed storage layer with page servers, which enables near-instantaneous scaling of compute resources by adding or removing compute nodes without data movement. However, this design does not support elastic query or cross-database query features because those rely on a shared metadata and transaction log that is not distributed across separate databases in the Hyperscale model. In practice, applications requiring cross-database queries must use alternative patterns like sharding or external data sources via PolyBase.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Plan and implement data platform resources — This question tests Plan and implement data platform resources — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Hyperscale does not support cross-database queries or elastic queries. — Option D is correct because Azure SQL Database Hyperscale does not support cross-database queries or elastic queries. This limitation is critical for the application team if they need to query across multiple databases in a single query, which is a common requirement for distributed applications. The Hyperscale architecture separates compute from storage, making cross-database query capabilities unavailable, unlike other service tiers such as General Purpose or Business Critical.
What should I do if I get this DP-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.