Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 49
Question 480
At Meadowbridge Services a proof-of-concept SQL database runs infrequent development tests. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: C
Join customers and orders only on a similar-looking surname. This concerns another issue: At Cedarcrest Finance invoices must display the correct customer account. In the stated case—At Meadowbridge Services a proof-of-concept SQL database runs infrequent development tests—reject: Assume a continuously saturated production database will pause and deliver large idle savings. The safer response is: Consider Azure SQL Database serverless compute for an eligible single database with intermittent activity.
Assume one exported spreadsheet is a fully supported transaction-consistent recovery mechanism. This concerns another issue: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. In the stated case—At Meadowbridge Services a proof-of-concept SQL database runs infrequent development tests—reject: Assume a continuously saturated production database will pause and deliver large idle savings. The safer response is: Consider Azure SQL Database serverless compute for an eligible single database with intermittent activity.
Assume a continuously saturated production database will pause and deliver large idle savings. The scenario is: At Meadowbridge Services a proof-of-concept SQL database runs infrequent development tests. This undermines the mechanism: Serverless can scale compute according to activity and support auto-pause where configured and supported. Instead: Consider Azure SQL Database serverless compute for an eligible single database with intermittent activity.
Assume every SQL Server instance feature exists unchanged in a single Azure SQL Database. This concerns another issue: At Silverline Finance an existing SQL Server application has linked workflows and instance requirements. In the stated case—At Meadowbridge Services a proof-of-concept SQL database runs infrequent development tests—reject: Assume a continuously saturated production database will pause and deliver large idle savings. The safer response is: Consider Azure SQL Database serverless compute for an eligible single database with intermittent activity.
Question 481
At Harborcrest Finance a long-lived transaction archive has rapid table growth. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: A
Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. This works because: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. The scenario is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. Verify the outcome by: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. This addresses a different situation: At Bayfield Travel application requests slow under concurrent booking loads. The present case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The relevant action here is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Choose Azure SQL Database for a new cloud relational application when a managed SQL database is preferred over server administration. This addresses a different situation: At Harborcrest Apps a new order service needs managed T-SQL storage. The present case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The relevant action here is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Apply NOT NULL and CHECK constraints when a field has mandatory business-valid ranges. This addresses a different situation: At Meadowline Manufacturing purchase quantities must be positive. The present case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The relevant action here is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Question 482
At Harborcrest Finance a long-lived transaction archive has rapid table growth. The team proposes this approach: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. Which technical principle explains the choice?
Answer & Explanations
Correct answer: A
Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. This principle supports the intervention: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. The relevant scenario is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. Verify the result by: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
The managed service supports MySQL-compatible workloads without requiring the team to operate the server VM. That explains a separate situation: At Meadowline Commerce a storefront relies on an existing MySQL schema. The current case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The actual mechanism is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior.
A view provides a defined query interface and can omit fields that consumers should not see. That explains a separate situation: At Cedarcrest Travel analysts need booking summaries without card tokens. The current case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The actual mechanism is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior.
Database connectivity requires permitted network paths and valid database identities independently of storing a password in code. That explains a separate situation: At Meadowbank Health only an approved application subnet should query a managed SQL database. The current case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The actual mechanism is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior.
Question 483
At Harborcrest Finance a long-lived transaction archive has rapid table growth. After implementing this approach—Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity—which result would most directly confirm success?
Answer & Explanations
Correct answer: A
Compare a large synthetic database growth and read workload against eligible Hyperscale limits. This tests the targeted action: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. The reason is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. The reported case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth.
Import a small MySQL test schema and verify client driver and query behavior. This tests a separate situation: At Meadowline Commerce a storefront relies on an existing MySQL schema. The observed case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. Use this acceptance check instead: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Connect from an allowed test application identity and verify a disallowed client cannot open the SQL session. This tests a separate situation: At Meadowbank Health only an approved application subnet should query a managed SQL database. The observed case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. Use this acceptance check instead: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Test a harmless quoted customer name and confirm it is treated as a value rather than a SQL operator. This tests a separate situation: At Silverport Retail a support page searches names containing apostrophes. The observed case is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. Use this acceptance check instead: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Question 484
At Harborcrest Finance a long-lived transaction archive has rapid table growth. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: D
Give every low-usage tenant its own permanently oversized dedicated compute tier. This concerns another issue: At Cedarcrest SaaS hundreds of customer databases have different peak usage periods. In the stated case—At Harborcrest Finance a long-lived transaction archive has rapid table growth—reject: Assume an in-memory cache alone permanently expands the relational database's durable storage. The safer response is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Select individual sale prices while labeling every row as the grand total. This concerns another issue: At Oakridge Supplies merchandising needs revenue by item family. In the stated case—At Harborcrest Finance a long-lived transaction archive has rapid table growth—reject: Assume an in-memory cache alone permanently expands the relational database's durable storage. The safer response is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Choose Azure SQL Database while demanding custom guest OS drivers inside its managed service. This concerns another issue: At Cedarwood Manufacturing a legacy SQL workload needs a specific supported OS-level extension. In the stated case—At Harborcrest Finance a long-lived transaction archive has rapid table growth—reject: Assume an in-memory cache alone permanently expands the relational database's durable storage. The safer response is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Assume an in-memory cache alone permanently expands the relational database's durable storage. The scenario is: At Harborcrest Finance a long-lived transaction archive has rapid table growth. The likely failure is: Data growth outstrips the chosen storage architecture. Instead: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Question 485
At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: D
Distinguish automatic service availability from application transaction retry and failover handling. This addresses a different situation: At Pinecrest Payments database failover should not charge a card twice. The present case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The relevant action here is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Treat SQL NULL as unknown or missing and use IS NULL instead of equality comparison when filtering it. This addresses a different situation: At Willowport Health incomplete patient contact records need review. The present case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The relevant action here is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Use an Azure SQL Database elastic pool for several databases with varying, noncoincident resource demand. This addresses a different situation: At Cedarcrest SaaS hundreds of customer databases have different peak usage periods. The present case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The relevant action here is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. This works because: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. The scenario is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Verify the outcome by: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Question 486
At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The team proposes this approach: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. Which technical principle explains the choice?
Answer & Explanations
Correct answer: B
Managed automatic backups support supported point-in-time restore windows, while retention settings govern recoverability. That explains a separate situation: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The current case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The actual mechanism is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior.
Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. This principle supports the intervention: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. The relevant scenario is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Verify the result by: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Engine family alone does not guarantee all self-managed plugins, versions or host customizations are supported by the managed offering. That explains a separate situation: At Oakridge Data a PostgreSQL service relies on a specialized geographic extension. The current case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The actual mechanism is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior.
A view provides a defined query interface and can omit fields that consumers should not see. That explains a separate situation: At Cedarcrest Travel analysts need booking summaries without card tokens. The current case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. The actual mechanism is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior.
Question 487
At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. After implementing this approach—Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity—which result would most directly confirm success?
Answer & Explanations
Correct answer: A
Compare a large synthetic database growth and read workload against eligible Hyperscale limits. This tests the targeted action: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity. The reason is: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. The reported case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas.
Inventory fictional extension dependencies and run a targeted proof-of-concept query on the selected Azure engine. This tests a separate situation: At Oakridge Data a PostgreSQL service relies on a specialized geographic extension. The observed case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Use this acceptance check instead: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Verify a test operator can administer the VM guest and supported SQL configuration required by the application. This tests a separate situation: At Cedarwood Manufacturing a legacy SQL workload needs a specific supported OS-level extension. The observed case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Use this acceptance check instead: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Query a test reporting view and confirm it excludes protected payment-token columns. This tests a separate situation: At Cedarcrest Travel analysts need booking summaries without card tokens. The observed case is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Use this acceptance check instead: Compare a large synthetic database growth and read workload against eligible Hyperscale limits.
Question 488
At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: C
Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. This concerns another issue: At Bayfield Travel application requests slow under concurrent booking loads. In the stated case—At Cedarbank Retail a large relational dataset requires multiple analytic read replicas—reject: Assume an in-memory cache alone permanently expands the relational database's durable storage. The safer response is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Open database access to every public address while sharing a master login in a repository. This concerns another issue: At Meadowbank Health only an approved application subnet should query a managed SQL database. In the stated case—At Cedarbank Retail a large relational dataset requires multiple analytic read replicas—reject: Assume an in-memory cache alone permanently expands the relational database's durable storage. The safer response is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Assume an in-memory cache alone permanently expands the relational database's durable storage. The scenario is: At Cedarbank Retail a large relational dataset requires multiple analytic read replicas. This undermines the mechanism: Hyperscale's storage and compute architecture targets large-scale SQL Database workloads with distinct storage scaling behavior. Instead: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Duplicate the order date on every line keyed by order ID and line number. This concerns another issue: At Cedarbrook Manufacturing order header details repeat across line items. In the stated case—At Cedarbank Retail a large relational dataset requires multiple analytic read replicas—reject: Assume an in-memory cache alone permanently expands the relational database's durable storage. The safer response is: Evaluate Azure SQL Database Hyperscale when a supported workload needs large database size and independently scalable read capacity.
Question 489
At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: B
Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. This addresses a different situation: At Bayfield Travel application requests slow under concurrent booking loads. The present case is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The relevant action here is: Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs.
Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs. This works because: Managed automatic backups support supported point-in-time restore windows, while retention settings govern recoverability. The scenario is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. Verify the outcome by: Restore a synthetic database to a timestamp before an accidental test delete.
Apply first-normal-form principles by placing repeatable phone numbers in a separate related table. This addresses a different situation: At Meadowport Services customers often provide multiple contact phones. The present case is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The relevant action here is: Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs.
Choose Azure SQL Database for a new cloud relational application when a managed SQL database is preferred over server administration. This addresses a different situation: At Harborcrest Apps a new order service needs managed T-SQL storage. The present case is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The relevant action here is: Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs.
Question 490
At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The team proposes this approach: Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs. Which technical principle explains the choice?
Answer & Explanations
Correct answer: C
Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. That explains a separate situation: At Bayfield Travel application requests slow under concurrent booking loads. The current case is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The actual mechanism is: Managed automatic backups support supported point-in-time restore windows, while retention settings govern recoverability.
Serverless can scale compute according to activity and support auto-pause where configured and supported. That explains a separate situation: At Pineport Research an internal reporting database is idle most evenings. The current case is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The actual mechanism is: Managed automatic backups support supported point-in-time restore windows, while retention settings govern recoverability.
Managed automatic backups support supported point-in-time restore windows, while retention settings govern recoverability. This principle supports the intervention: Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs. The relevant scenario is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. Verify the result by: Restore a synthetic database to a timestamp before an accidental test delete.
GROUP BY partitions rows into categories and aggregate functions calculate a result per category. That explains a separate situation: At Oakridge Supplies merchandising needs revenue by item family. The current case is: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The actual mechanism is: Managed automatic backups support supported point-in-time restore windows, while retention settings govern recoverability.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- Microsoft DP-900 Practice Test 47 - 10 Questions (Last Reviewed 03-Oct-2026)
- Microsoft DP-900 Practice Test 48 - 10 Questions (Last Reviewed 02-Oct-2026)
- Microsoft DP-900 Practice Test 49 - 10 Questions (Last Reviewed 01-Oct-2026)
- Microsoft DP-900 Practice Test 50 - 10 Questions (Last Reviewed 30-Sep-2026)
- Microsoft DP-900 Practice Test 51 - 10 Questions (Last Reviewed 29-Sep-2026)