Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 56
Question 550
At Oakview Logistics old shipment manifests need occasional direct downloads. The team proposes this approach: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects. Which technical principle explains the choice?
Answer & Explanations
Correct answer: A
Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges. This principle supports the intervention: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects. The relevant scenario is: At Oakview Logistics old shipment manifests need occasional direct downloads. Verify the result by: Retrieve an older fictional monthly report directly and compare total expected storage and read costs.
API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering. That explains a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The current case is: At Oakview Logistics old shipment manifests need occasional direct downloads. The actual mechanism is: Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges.
A hierarchical namespace supports file and directory-oriented operations that differ from flat blob-name prefixes. That explains a separate situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The current case is: At Oakview Logistics old shipment manifests need occasional direct downloads. The actual mechanism is: Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges.
A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. That explains a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The current case is: At Oakview Logistics old shipment manifests need occasional direct downloads. The actual mechanism is: Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges.
Question 551
At Oakview Logistics old shipment manifests need occasional direct downloads. After implementing this approach—Use an appropriate cool or cold blob tier for infrequently accessed but still online objects—which result would most directly confirm success?
Answer & Explanations
Correct answer: A
Retrieve an older fictional monthly report directly and compare total expected storage and read costs. This tests the targeted action: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects. The reason is: Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges. The reported case is: At Oakview Logistics old shipment manifests need occasional direct downloads.
Run a representative test using the application's MongoDB driver and verify its required operations. This tests a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The observed case is: At Oakview Logistics old shipment manifests need occasional direct downloads. Use this acceptance check instead: Retrieve an older fictional monthly report directly and compare total expected storage and read costs.
Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected. This tests a separate situation: At Silverlake Media a partner needs temporary read access to one approved asset. The observed case is: At Oakview Logistics old shipment manifests need occasional direct downloads. Use this acceptance check instead: Retrieve an older fictional monthly report directly and compare total expected storage and read costs.
Organize fictional partitioned data under dated directories and verify directory-level move or access behavior. This tests a separate situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The observed case is: At Oakview Logistics old shipment manifests need occasional direct downloads. Use this acceptance check instead: Retrieve an older fictional monthly report directly and compare total expected storage and read costs.
Question 552
At Oakview Logistics old shipment manifests need occasional direct downloads. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: D
Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys. This concerns another issue: At Harborpoint IoT device status values are accessed by tenant and device ID. In the stated case—At Oakview Logistics old shipment manifests need occasional direct downloads—reject: Assume every rare-access object must be archived offline even when prompt retrieval is required. The safer response is: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects.
Assume locally redundant copies within one site protect against every regional disaster. This concerns another issue: At Cedarbank Payments retained transaction exports require defined regional resilience. In the stated case—At Oakview Logistics old shipment manifests need occasional direct downloads—reject: Assume every rare-access object must be archived offline even when prompt retrieval is required. The safer response is: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects.
Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. This concerns another issue: At Cedarfield Apps developers build a new JSON-first profile service. In the stated case—At Oakview Logistics old shipment manifests need occasional direct downloads—reject: Assume every rare-access object must be archived offline even when prompt retrieval is required. The safer response is: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects.
Assume every rare-access object must be archived offline even when prompt retrieval is required. The scenario is: At Oakview Logistics old shipment manifests need occasional direct downloads. The likely failure is: Time-sensitive regulatory requests cannot be fulfilled promptly. Instead: Use an appropriate cool or cold blob tier for infrequently accessed but still online objects.
Question 553
At Cedarbank Records files legally retained for a decade are rarely requested. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: B
Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. This addresses a different situation: At Harborland Securities trade evidence requires enforced retention. The present case is: At Cedarbank Records files legally retained for a decade are rarely requested. The relevant action here is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. This works because: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. The scenario is: At Cedarbank Records files legally retained for a decade are rarely requested. Verify the outcome by: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. This addresses a different situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The present case is: At Cedarbank Records files legally retained for a decade are rarely requested. The relevant action here is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Store large binary images and backups as blobs in Azure Blob Storage with appropriate container access policies. This addresses a different situation: At Harborcrest Media hundreds of thousands of images need private object storage. The present case is: At Cedarbank Records files legally retained for a decade are rarely requested. The relevant action here is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Question 554
At Cedarbank Records files legally retained for a decade are rarely requested. The team proposes this approach: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. Which technical principle explains the choice?
Answer & Explanations
Correct answer: A
Archived blob data requires rehydration before normal online access and has special retention/cost constraints. This principle supports the intervention: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. The relevant scenario is: At Cedarbank Records files legally retained for a decade are rarely requested. Verify the result by: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Partition keys determine entity grouping and affect efficient lookup and potential hot partitions. That explains a separate situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The current case is: At Cedarbank Records files legally retained for a decade are rarely requested. The actual mechanism is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. That explains a separate situation: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The current case is: At Cedarbank Records files legally retained for a decade are rarely requested. The actual mechanism is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. That explains a separate situation: At Pineport Retail product searches consume more resources than simple ID reads. The current case is: At Cedarbank Records files legally retained for a decade are rarely requested. The actual mechanism is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
Question 555
At Cedarbank Records files legally retained for a decade are rarely requested. After implementing this approach—Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
Compare a representative query and insert workload before and after adjusting a test indexing policy. This tests a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The observed case is: At Cedarbank Records files legally retained for a decade are rarely requested. Use this acceptance check instead: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Restore one fictional archived backup in a controlled test and record the observed recovery process. This tests the targeted action: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. The reason is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. The reported case is: At Cedarbank Records files legally retained for a decade are rarely requested.
Test that a report service reads one permitted container but cannot list a protected unrelated container. This tests a separate situation: At Meadowcrest Banking one analytics service reads a restricted statements container. The observed case is: At Cedarbank Records files legally retained for a decade are rarely requested. Use this acceptance check instead: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Create test objects with different prefixes and verify only the approved eligible prefix changes tier. This tests a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The observed case is: At Cedarbank Records files legally retained for a decade are rarely requested. Use this acceptance check instead: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Question 556
At Cedarbank Records files legally retained for a decade are rarely requested. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: B
Grant subscription-wide owner access solely to read a single blob. This concerns another issue: At Meadowcrest Banking one analytics service reads a restricted statements container. In the stated case—At Cedarbank Records files legally retained for a decade are rarely requested—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Promise an instant restore from archive without planning rehydration. The scenario is: At Cedarbank Records files legally retained for a decade are rarely requested. This undermines the mechanism: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. Instead: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Publish a perpetual account-level SAS with write and delete rights for a one-file download. This concerns another issue: At Silverlake Media a partner needs temporary read access to one approved asset. In the stated case—At Cedarbank Records files legally retained for a decade are rarely requested—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Assume a single-region local file database automatically delivers globally distributed consistency. This concerns another issue: At Silverbrook Commerce customers in several continents update shopping preferences. In the stated case—At Cedarbank Records files legally retained for a decade are rarely requested—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Question 557
At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: B
Select the hot blob access tier for objects read frequently despite higher storage cost. This addresses a different situation: At Pinefield Retail product images are fetched continuously by shoppers. The present case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The relevant action here is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. This works because: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. The scenario is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Verify the outcome by: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. This addresses a different situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The present case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The relevant action here is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. This addresses a different situation: At Silverlake Media a partner needs temporary read access to one approved asset. The present case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The relevant action here is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Question 558
At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The team proposes this approach: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. Which technical principle explains the choice?
Answer & Explanations
Correct answer: D
The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. That explains a separate situation: At Harborview Retail inventory changes feed a search-index updater. The current case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The actual mechanism is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. That explains a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The current case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The actual mechanism is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
A hierarchical namespace supports file and directory-oriented operations that differ from flat blob-name prefixes. That explains a separate situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The current case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. The actual mechanism is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
Archived blob data requires rehydration before normal online access and has special retention/cost constraints. This principle supports the intervention: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. The relevant scenario is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Verify the result by: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Question 559
At Harborline Research immutable experiment archives must be retrievable within a planned lead time. After implementing this approach—Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable—which result would most directly confirm success?
Answer & Explanations
Correct answer: C
Create test objects with different prefixes and verify only the approved eligible prefix changes tier. This tests a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The observed case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Use this acceptance check instead: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Mount a synthetic file share from two approved hosts and verify both can read a test document. This tests a separate situation: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The observed case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Use this acceptance check instead: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Restore one fictional archived backup in a controlled test and record the observed recovery process. This tests the targeted action: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. The reason is: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. The reported case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time.
Write a synthetic value and test subsequent reads across configured clients and regions. This tests a separate situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The observed case is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Use this acceptance check instead: Restore one fictional archived backup in a controlled test and record the observed recovery process.
Question 560
At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Promise an instant restore from archive without planning rehydration. The scenario is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. This undermines the mechanism: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. Instead: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Assume every rare-access object must be archived offline even when prompt retrieval is required. This concerns another issue: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. In the stated case—At Harborline Research immutable experiment archives must be retrievable within a planned lead time—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Provision throughput based only on storage capacity without testing query complexity. This concerns another issue: At Pineport Retail product searches consume more resources than simple ID reads. In the stated case—At Harborline Research immutable experiment archives must be retrievable within a planned lead time—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Put daily application assets directly into archive tier to minimize storage price alone. This concerns another issue: At Pinefield Retail product images are fetched continuously by shoppers. In the stated case—At Harborline Research immutable experiment archives must be retrievable within a planned lead time—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- Microsoft DP-900 Practice Test 54 - 10 Questions (Last Reviewed 26-Sep-2026)
- Microsoft DP-900 Practice Test 55 - 10 Questions (Last Reviewed 25-Sep-2026)
- Microsoft DP-900 Practice Test 56 - 10 Questions (Last Reviewed 24-Sep-2026)
- Microsoft DP-900 Practice Test 57 - 10 Questions (Last Reviewed 19-Nov-2026)
- Microsoft DP-900 Practice Test 58 - 10 Questions (Last Reviewed 18-Nov-2026)