Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 58
Question 570
At Meadowfield Accounting two virtual machines share legacy report files through SMB. The team proposes this approach: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. Which technical principle explains the choice?
Answer & Explanations
Correct answer: D
Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. That explains a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The current case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins. That explains a separate situation: At Harborpoint IoT device status values are accessed by tenant and device ID. The current case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges. That explains a separate situation: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. The current case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. This principle supports the intervention: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. The relevant scenario is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. Verify the result by: Mount a synthetic file share from two approved hosts and verify both can read a test document.
Question 571
At Meadowfield Accounting two virtual machines share legacy report files through SMB. After implementing this approach—Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs—which result would most directly confirm success?
Answer & Explanations
Correct answer: D
Restore one fictional archived backup in a controlled test and record the observed recovery process. This tests a separate situation: At Cedarbank Records files legally retained for a decade are rarely requested. The observed case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. Use this acceptance check instead: Mount a synthetic file share from two approved hosts and verify both can read a test document.
Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan. This tests a separate situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The observed case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. Use this acceptance check instead: Mount a synthetic file share from two approved hosts and verify both can read a test document.
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 Meadowfield Accounting two virtual machines share legacy report files through SMB. Use this acceptance check instead: Mount a synthetic file share from two approved hosts and verify both can read a test document.
Mount a synthetic file share from two approved hosts and verify both can read a test document. This tests the targeted action: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. The reason is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. The reported case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB.
Question 572
At Meadowfield Accounting two virtual machines share legacy report files through SMB. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: D
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 Meadowfield Accounting two virtual machines share legacy report files through SMB—reject: Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The safer response is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Put every large image into an Azure Table Storage entity expecting full binary-object semantics. This concerns another issue: At Harborcrest Media hundreds of thousands of images need private object storage. In the stated case—At Meadowfield Accounting two virtual machines share legacy report files through SMB—reject: Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The safer response is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Remove every indexed path even though the production app filters on nested document fields. This concerns another issue: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. In the stated case—At Meadowfield Accounting two virtual machines share legacy report files through SMB—reject: Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The safer response is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The scenario is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The likely failure is: Applications depending on file shares fail. Instead: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Question 573
At Silverbrook Engineering Linux applications expect a shared NFS directory. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: B
Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. This addresses a different situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The present case is: At Silverbrook Engineering Linux applications expect a shared NFS directory. The relevant action here is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. This works because: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. The scenario is: At Silverbrook Engineering Linux applications expect a shared NFS directory. Verify the outcome by: Mount a synthetic file share from two approved hosts and verify both can read a test document.
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 Silverbrook Engineering Linux applications expect a shared NFS directory. The relevant action here is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. This addresses a different situation: At Cedarbank Payments retained transaction exports require defined regional resilience. The present case is: At Silverbrook Engineering Linux applications expect a shared NFS directory. The relevant action here is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Question 574
At Silverbrook Engineering Linux applications expect a shared NFS directory. The team proposes this approach: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. Which technical principle explains the choice?
Answer & Explanations
Correct answer: D
Archived blob data requires rehydration before normal online access and has special retention/cost constraints. That explains a separate situation: At Cedarbank Records files legally retained for a decade are rarely requested. The current case is: At Silverbrook Engineering Linux applications expect a shared NFS directory. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
Blob access tiers trade storage price for retrieval and transaction costs according to access frequency. That explains a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The current case is: At Silverbrook Engineering Linux applications expect a shared NFS directory. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
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 Silverbrook Engineering Linux applications expect a shared NFS directory. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. This principle supports the intervention: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. The relevant scenario is: At Silverbrook Engineering Linux applications expect a shared NFS directory. Verify the result by: Mount a synthetic file share from two approved hosts and verify both can read a test document.
Question 575
At Silverbrook Engineering Linux applications expect a shared NFS directory. After implementing this approach—Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
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 Silverbrook Engineering Linux applications expect a shared NFS directory. Use this acceptance check instead: Mount a synthetic file share from two approved hosts and verify both can read a test document.
Mount a synthetic file share from two approved hosts and verify both can read a test document. This tests the targeted action: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. The reason is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. The reported case is: At Silverbrook Engineering Linux applications expect a shared NFS directory.
Query one tenant's fictional records by partition and row key while measuring request behavior. This tests a separate situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The observed case is: At Silverbrook Engineering Linux applications expect a shared NFS directory. Use this acceptance check instead: Mount a synthetic file share from two approved hosts and verify both can read a test document.
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 Silverbrook Engineering Linux applications expect a shared NFS directory. Use this acceptance check instead: Mount a synthetic file share from two approved hosts and verify both can read a test document.
Question 576
At Silverbrook Engineering Linux applications expect a shared NFS directory. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: D
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 Silverbrook Engineering Linux applications expect a shared NFS directory—reject: Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The safer response is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Put every large image into an Azure Table Storage entity expecting full binary-object semantics. This concerns another issue: At Harborcrest Media hundreds of thousands of images need private object storage. In the stated case—At Silverbrook Engineering Linux applications expect a shared NFS directory—reject: Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The safer response is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
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 Silverbrook Engineering Linux applications expect a shared NFS directory—reject: Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The safer response is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. The scenario is: At Silverbrook Engineering Linux applications expect a shared NFS directory. The likely failure is: Applications depending on file shares fail. Instead: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
Question 577
At Harborpoint IoT device status values are accessed by tenant and device ID. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: B
Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. This addresses a different situation: At Cedarbank Records files legally retained for a decade are rarely requested. The present case is: At Harborpoint IoT device status values are accessed by tenant and device ID. The relevant action here is: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys. This works because: Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins. The scenario is: At Harborpoint IoT device status values are accessed by tenant and device ID. Verify the outcome by: Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. This addresses a different situation: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The present case is: At Harborpoint IoT device status values are accessed by tenant and device ID. The relevant action here is: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. This addresses a different situation: At Silverbrook Commerce customers in several continents update shopping preferences. The present case is: At Harborpoint IoT device status values are accessed by tenant and device ID. The relevant action here is: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Question 578
At Harborpoint IoT device status values are accessed by tenant and device ID. The team proposes this approach: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys. Which technical principle explains the choice?
Answer & Explanations
Correct answer: D
Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. That explains a separate situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The current case is: At Harborpoint IoT device status values are accessed by tenant and device ID. The actual mechanism is: Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins.
Management-plane roles and data-access permissions do not automatically mean the same thing, so users need appropriate scoped data access. That explains a separate situation: At Meadowcrest Banking one analytics service reads a restricted statements container. The current case is: At Harborpoint IoT device status values are accessed by tenant and device ID. The actual mechanism is: Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins.
SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. That explains a separate situation: At Silverlake Media a partner needs temporary read access to one approved asset. The current case is: At Harborpoint IoT device status values are accessed by tenant and device ID. The actual mechanism is: Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins.
Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins. This principle supports the intervention: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys. The relevant scenario is: At Harborpoint IoT device status values are accessed by tenant and device ID. Verify the result by: Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
Question 579
At Harborpoint IoT device status values are accessed by tenant and device ID. After implementing this approach—Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
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 Harborpoint IoT device status values are accessed by tenant and device ID. Use this acceptance check instead: Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match. This tests the targeted action: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys. The reason is: Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins. The reported case is: At Harborpoint IoT device status values are accessed by tenant and device ID.
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 Harborpoint IoT device status values are accessed by tenant and device ID. Use this acceptance check instead: Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
Update a fictional order item and verify the consumer receives the change once under idempotent processing. This tests a separate situation: At Harborview Retail inventory changes feed a search-index updater. The observed case is: At Harborpoint IoT device status values are accessed by tenant and device ID. Use this acceptance check instead: Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
Question 580
At Harborpoint IoT device status values are accessed by tenant and device ID. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys. The scenario is: At Harborpoint IoT device status values are accessed by tenant and device ID. This undermines the mechanism: Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins. Instead: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Apply immediate deletion across all containers without checking compliance retention. This concerns another issue: At Westlake Finance statement exports move from hot to cool after an approved interval. In the stated case—At Harborpoint IoT device status values are accessed by tenant and device ID—reject: Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys. The safer response is: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Re-export the entire container for every notification and assume no duplicate updates can occur. This concerns another issue: At Harborview Retail inventory changes feed a search-index updater. In the stated case—At Harborpoint IoT device status values are accessed by tenant and device ID—reject: Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys. The safer response is: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Grant ordinary application users delete rights to all archived compliance evidence. This concerns another issue: At Harborland Securities trade evidence requires enforced retention. In the stated case—At Harborpoint IoT device status values are accessed by tenant and device ID—reject: Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys. The safer response is: Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- 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)
- Microsoft DP-900 Practice Test 59 - 10 Questions (Last Reviewed 17-Nov-2026)
- Microsoft DP-900 Practice Test 60 - 10 Questions (Last Reviewed 16-Nov-2026)