Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 52
Question 510
At Harborland Logistics a managed SQL service briefly reconnects during maintenance. The team proposes this approach: Distinguish automatic service availability from application transaction retry and failover handling. Which technical principle explains the choice?
Answer & Explanations
Correct answer: B
The IaaS model leaves OS, SQL Server configuration and much patch responsibility with the customer. That explains a separate situation: At Cedarwood Manufacturing a legacy SQL workload needs a specific supported OS-level extension. The current case is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. The actual mechanism is: Platform-managed high availability protects eligible infrastructure failures, but clients must tolerate transient connection errors.
Platform-managed high availability protects eligible infrastructure failures, but clients must tolerate transient connection errors. This principle supports the intervention: Distinguish automatic service availability from application transaction retry and failover handling. The relevant scenario is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. Verify the result by: Trigger a controlled connection interruption and verify the application retries idempotent operations safely.
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 Harborland Logistics a managed SQL service briefly reconnects during maintenance. The actual mechanism is: Platform-managed high availability protects eligible infrastructure failures, but clients must tolerate transient connection errors.
SQL result ordering is not guaranteed without an explicit sort clause. That explains a separate situation: At Cedarbank Logistics dispatch lists must show oldest outstanding shipments first. The current case is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. The actual mechanism is: Platform-managed high availability protects eligible infrastructure failures, but clients must tolerate transient connection errors.
Question 511
At Harborland Logistics a managed SQL service briefly reconnects during maintenance. After implementing this approach—Distinguish automatic service availability from application transaction retry and failover handling—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change. This tests a separate situation: At Bayfield Travel application requests slow under concurrent booking loads. The observed case is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. Use this acceptance check instead: Trigger a controlled connection interruption and verify the application retries idempotent operations safely.
Trigger a controlled connection interruption and verify the application retries idempotent operations safely. This tests the targeted action: Distinguish automatic service availability from application transaction retry and failover handling. The reason is: Platform-managed high availability protects eligible infrastructure failures, but clients must tolerate transient connection errors. The reported case is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance.
Generate staggered synthetic tenant loads and inspect whether pooled capacity meets service targets. This tests a separate situation: At Cedarcrest SaaS hundreds of customer databases have different peak usage periods. The observed case is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. Use this acceptance check instead: Trigger a controlled connection interruption and verify the application retries idempotent operations safely.
Query a sample customer without an email address using IS NULL and verify it appears. This tests a separate situation: At Willowport Health incomplete patient contact records need review. The observed case is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. Use this acceptance check instead: Trigger a controlled connection interruption and verify the application retries idempotent operations safely.
Question 512
At Harborland Logistics a managed SQL service briefly reconnects during maintenance. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Treat any transient SQL connection reset as an instruction to blindly double-submit the same payment. The scenario is: At Harborland Logistics a managed SQL service briefly reconnects during maintenance. This undermines the mechanism: Platform-managed high availability protects eligible infrastructure failures, but clients must tolerate transient connection errors. Instead: Distinguish automatic service availability from application transaction retry and failover handling.
Assume every self-hosted PostgreSQL extension can be installed with root OS access in a managed database. This concerns another issue: At Oakridge Data a PostgreSQL service relies on a specialized geographic extension. In the stated case—At Harborland Logistics a managed SQL service briefly reconnects during maintenance—reject: Treat any transient SQL connection reset as an instruction to blindly double-submit the same payment. The safer response is: Distinguish automatic service availability from application transaction retry and failover handling.
Put COUNT(*) in a row-level WHERE clause and expect every database to accept it. This concerns another issue: At Meadowcrest Insurance analysts need branches exceeding an incident threshold. In the stated case—At Harborland Logistics a managed SQL service briefly reconnects during maintenance—reject: Treat any transient SQL connection reset as an instruction to blindly double-submit the same payment. The safer response is: Distinguish automatic service availability from application transaction retry and failover handling.
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 Harborland Logistics a managed SQL service briefly reconnects during maintenance—reject: Treat any transient SQL connection reset as an instruction to blindly double-submit the same payment. The safer response is: Distinguish automatic service availability from application transaction retry and failover handling.
Question 513
At Bayfield Travel application requests slow under concurrent booking loads. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: D
Use a foreign key between order lines and their parent orders to enforce a valid relationship. This addresses a different situation: At Silvercrest Commerce all invoice lines must belong to an existing order. The present case is: At Bayfield Travel application requests slow under concurrent booking loads. The relevant action here is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Plan a managed Azure SQL backup retention and point-in-time restore strategy aligned to business recovery needs. This addresses a different situation: At Silverlake Insurance a mistaken data delete must be recoverable from earlier in the day. The present case is: At Bayfield Travel application requests slow under concurrent booking loads. The relevant action here is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
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 Bayfield Travel application requests slow under concurrent booking loads. The relevant action here is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. This works because: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. The scenario is: At Bayfield Travel application requests slow under concurrent booking loads. Verify the outcome by: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Question 514
At Bayfield Travel application requests slow under concurrent booking loads. The team proposes this approach: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. Which technical principle explains the choice?
Answer & Explanations
Correct answer: C
Managed Instance supports many instance-level SQL Server capabilities while retaining managed infrastructure operations. That explains a separate situation: At Silverline Finance an existing SQL Server application has linked workflows and instance requirements. The current case is: At Bayfield Travel application requests slow under concurrent booking loads. The actual mechanism is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.
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 Bayfield Travel application requests slow under concurrent booking loads. The actual mechanism is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.
Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. This principle supports the intervention: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. The relevant scenario is: At Bayfield Travel application requests slow under concurrent booking loads. Verify the result by: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Relational constraints reject invalid rows at the database boundary independent of application forms. That explains a separate situation: At Meadowline Manufacturing purchase quantities must be positive. The current case is: At Bayfield Travel application requests slow under concurrent booking loads. The actual mechanism is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.
Question 515
At Bayfield Travel application requests slow under concurrent booking loads. After implementing this approach—Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
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 Bayfield Travel application requests slow under concurrent booking loads. Use this acceptance check instead: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change. This tests the targeted action: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. The reason is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. The reported case is: At Bayfield Travel application requests slow under concurrent booking loads.
Insert a test line for an absent order ID and confirm the database rejects the reference. This tests a separate situation: At Silvercrest Commerce all invoice lines must belong to an existing order. The observed case is: At Bayfield Travel application requests slow under concurrent booking loads. Use this acceptance check instead: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
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 Bayfield Travel application requests slow under concurrent booking loads. Use this acceptance check instead: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Question 516
At Bayfield Travel application requests slow under concurrent booking loads. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: D
Concatenate untrusted search input directly into a SELECT string. This concerns another issue: At Silverport Retail a support page searches names containing apostrophes. In the stated case—At Bayfield Travel application requests slow under concurrent booking loads—reject: Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The safer response is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Assume a continuously saturated production database will pause and deliver large idle savings. This concerns another issue: At Pineport Research an internal reporting database is idle most evenings. In the stated case—At Bayfield Travel application requests slow under concurrent booking loads—reject: Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The safer response is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
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 Bayfield Travel application requests slow under concurrent booking loads—reject: Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The safer response is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The scenario is: At Bayfield Travel application requests slow under concurrent booking loads. The likely failure is: Costs increase while query latency remains high. Instead: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Question 517
At Silverpoint Media growing API traffic stresses a relational database. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: C
Normalize customer city reference details to remove transitive dependencies when those details are shared. This addresses a different situation: At Harborcrest Tax a postal region's standard reference data changes annually. The present case is: At Silverpoint Media growing API traffic stresses a relational database. The relevant action here is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
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 Silverpoint Media growing API traffic stresses a relational database. The relevant action here is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. This works because: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. The scenario is: At Silverpoint Media growing API traffic stresses a relational database. Verify the outcome by: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
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 Silverpoint Media growing API traffic stresses a relational database. The relevant action here is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Question 518
At Silverpoint Media growing API traffic stresses a relational database. The team proposes this approach: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. Which technical principle explains the choice?
Answer & Explanations
Correct answer: D
The IaaS model leaves OS, SQL Server configuration and much patch responsibility with the customer. That explains a separate situation: At Cedarwood Manufacturing a legacy SQL workload needs a specific supported OS-level extension. The current case is: At Silverpoint Media growing API traffic stresses a relational database. The actual mechanism is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.
Attributes dependent only on a portion of a composite key belong in a parent table rather than every line. That explains a separate situation: At Cedarbrook Manufacturing order header details repeat across line items. The current case is: At Silverpoint Media growing API traffic stresses a relational database. The actual mechanism is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.
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 Silverpoint Media growing API traffic stresses a relational database. The actual mechanism is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.
Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. This principle supports the intervention: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. The relevant scenario is: At Silverpoint Media growing API traffic stresses a relational database. Verify the result by: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Question 519
At Silverpoint Media growing API traffic stresses a relational database. After implementing this approach—Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
Run a test compatibility inventory for instance-dependent jobs and confirm supported behaviors on the candidate service. This tests a separate situation: At Silverline Finance an existing SQL Server application has linked workflows and instance requirements. The observed case is: At Silverpoint Media growing API traffic stresses a relational database. Use this acceptance check instead: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change. This tests the targeted action: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints. The reason is: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. The reported case is: At Silverpoint Media growing API traffic stresses a relational database.
Change a sample order date once and verify all associated line records reflect the parent change. This tests a separate situation: At Cedarbrook Manufacturing order header details repeat across line items. The observed case is: At Silverpoint Media growing API traffic stresses a relational database. Use this acceptance check instead: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
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 Silverpoint Media growing API traffic stresses a relational database. Use this acceptance check instead: Run a synthetic peak query mix and inspect resource metrics before and after a justified tier change.
Question 520
At Silverpoint Media growing API traffic stresses a relational database. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: C
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 Silverpoint Media growing API traffic stresses a relational database—reject: Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The safer response is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Select SQL Server only because both systems support SQL-like queries and assume drivers are interchangeable. This concerns another issue: At Meadowline Commerce a storefront relies on an existing MySQL schema. In the stated case—At Silverpoint Media growing API traffic stresses a relational database—reject: Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The safer response is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The scenario is: At Silverpoint Media growing API traffic stresses a relational database. This undermines the mechanism: Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. Instead: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
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 Silverpoint Media growing API traffic stresses a relational database—reject: Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. The safer response is: Scale Azure SQL compute based on observed CPU, IO, concurrent sessions and service-tier constraints.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- 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)
- Microsoft DP-900 Practice Test 52 - 10 Questions (Last Reviewed 28-Sep-2026)
- Microsoft DP-900 Practice Test 53 - 10 Questions (Last Reviewed 27-Sep-2026)
- Microsoft DP-900 Practice Test 54 - 10 Questions (Last Reviewed 26-Sep-2026)