Topic 06 Practice Test 2 covers Azure Files and Blob Storage for Microsoft Azure Administrator AZ-104 and maps to the objective: Configure Azure Files and Azure Blob Storage. For broader exam preparation, review the Microsoft AZ-104 Exam Dumps. Every option includes focused technical reasoning explaining both the Azure concept and its fit to the scenario.
Question 1
Wingtip Toys needs protection from an administrator accidentally deleting an entire blob container. Which feature should be enabled? Choose ONE.
- Enable container soft delete
- Enable blob soft delete
- Enable blob versioning
- Enable soft delete for Azure file shares
Correct Answer: A
Correct Answer
Answer A is correct because The scenario for Wingtip Toys requires this result: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. This directly addresses it.
Incorrect Answers
Answer B is incorrect because The required outcome for Wingtip Toys is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This capability does not satisfy that condition.
Answer C is incorrect because The requirement for Wingtip Toys is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. The option therefore targets a different Azure capability.
Answer D is incorrect because Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. The mismatch for Wingtip Toys is the stated requirement: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Question 2
- Datum already protects individual blobs but now wants recovery after deletion of the container itself. What additional protection is required? Choose ONE.
- Enable blob soft delete
- Enable container soft delete
- Enable blob versioning
- Enable soft delete for Azure file shares
Correct Answer: B
Correct Answer
Answer B is correct because Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. It is the suitable choice for A. Datum; the deciding requirement is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Incorrect Answers
Answer A is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. The A. Datum scenario instead calls for this outcome: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Answer C is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. This would not resolve the stated requirement for A. Datum: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Answer D is incorrect because In the A. Datum case, the required result is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. Selecting this would solve a neighboring problem instead.
Question 3
Fourth Coffee wants a deleted blob container to remain recoverable for a defined retention period. Which setting addresses this failure mode? Choose ONE.
- Enable blob soft delete
- Enable blob versioning
- Enable container soft delete
- Enable soft delete for Azure file shares
Correct Answer: C
Correct Answer
Answer C is correct because For Fourth Coffee, the required behavior is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. That is why this option fits.
Incorrect Answers
Answer A is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. That feature is valid Azure functionality, but The requirement for Fourth Coffee is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Answer B is incorrect because For Fourth Coffee, the required behavior is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. That is not the behavior this scenario calls for.
Answer D is incorrect because Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. That does not line up with the stated constraint for Fourth Coffee: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Question 4
Lucerne Publishing is designing for accidental removal of a container rather than just deletion of a blob inside it. Which feature should it configure? Choose ONE.
- Enable blob soft delete
- Enable blob versioning
- Enable soft delete for Azure file shares
- Enable container soft delete
Correct Answer: D
Correct Answer
Answer D is correct because Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. The technical fit for Lucerne Publishing is direct because the requirement is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Incorrect Answers
Answer A is incorrect because For Lucerne Publishing, the deciding constraint is: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This solves a different operational need.
Answer B is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. Even though the feature can be useful, it does not provide The required outcome for Lucerne Publishing: an accidentally deleted blob container and its contents must be recoverable as a container-level unit.
Answer C is incorrect because The Lucerne Publishing scenario is testing this requirement: an accidentally deleted blob container and its contents must be recoverable as a container-level unit. Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. This option does not provide that result.
Question 5
Contoso plans a risky application upgrade and wants a point-in-time copy of an Azure file share immediately before deployment. What should it create? Choose ONE.
- Create an Azure Files share snapshot
- Enable soft delete for Azure file shares
- Enable blob soft delete
- Enable blob versioning
Correct Answer: A
Correct Answer
Answer A is correct because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. For Contoso, that directly matches the stated requirement: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Incorrect Answers
Answer B is incorrect because Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. It misses the key condition in the Contoso case: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Answer C is incorrect because Contoso must satisfy this condition: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This option is aimed at another design goal.
Answer D is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. Contoso needs a different capability; the required result is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Question 6
Fabrikam needs to restore an earlier version of a file after an application overwrites it on an Azure file share. Which protection mechanism is appropriate? Choose ONE.
- Enable soft delete for Azure file shares
- Create an Azure Files share snapshot
- Enable blob soft delete
- Enable blob versioning
Correct Answer: B
Correct Answer
Answer B is correct because The required outcome for Fabrikam is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. This option provides that capability.
Incorrect Answers
Answer A is incorrect because The requirement for Fabrikam is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. The option therefore targets a different Azure capability.
Answer C is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. The mismatch for Fabrikam is the stated requirement: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Answer D is incorrect because The Fabrikam design calls for this outcome: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. This choice addresses another concern.
Question 7
Northwind Traders wants periodic point-in-time recovery points for a file share and the ability to restore individual files. What should it use? Choose ONE.
- Enable soft delete for Azure file shares
- Enable blob soft delete
- Create an Azure Files share snapshot
- Enable blob versioning
Correct Answer: C
Correct Answer
Answer C is correct because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. The deciding condition in The Northwind Traders scenario is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. This option fits that condition.
Incorrect Answers
Answer A is incorrect because Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. This would not resolve the stated requirement for Northwind Traders: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Answer B is incorrect because In the Northwind Traders case, the required result is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. Selecting this would solve a neighboring problem instead.
Answer D is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. It is not the appropriate selection for Northwind Traders; the scenario requires: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Question 8
Adventure Works needs a read-only point-in-time copy of an Azure file share before a bulk content update. Which feature should the administrator create? Choose ONE.
- Enable soft delete for Azure file shares
- Enable blob soft delete
- Enable blob versioning
- Create an Azure Files share snapshot
Correct Answer: D
Correct Answer
Answer D is correct because The key requirement for Adventure Works is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes.
Incorrect Answers
Answer A is incorrect because For Adventure Works, the required behavior is: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes. Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. That is not the behavior this scenario calls for.
Answer B is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. That does not line up with the stated constraint for Adventure Works: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Answer C is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. For Adventure Works, however, that does not meet the stated requirement: a point-in-time read-only copy of an Azure file share is needed to recover earlier file content after unwanted changes.
Question 9
Tailspin Toys wants blobs to move to a cooler tier after 30 days and be deleted after 365 days without a scheduled script. What should it configure? Choose ONE.
- Configure an Azure Blob lifecycle management policy
- Enable blob versioning
- Enable blob soft delete
- Use the archive access tier
Correct Answer: A
Correct Answer
Answer A is correct because Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met. This aligns with The Tailspin Toys scenario, whose requirement is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Incorrect Answers
Answer B is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. Even though the feature can be useful, it does not provide The required outcome for Tailspin Toys: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Answer C is incorrect because The Tailspin Toys scenario is testing this requirement: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This option does not provide that result.
Answer D is incorrect because The required outcome for Tailspin Toys is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. The archive tier has the lowest storage cost for long-lived block blobs but data is offline and must be rehydrated before it can be read or modified. This capability does not satisfy that condition.
Question 10
Woodgrove Bank must automatically delete old blob versions after a retention period and tier aging base blobs. Which Azure Storage feature is designed for this? Choose ONE.
- Enable blob versioning
- Configure an Azure Blob lifecycle management policy
- Enable blob soft delete
- Use the archive access tier
Correct Answer: B
Correct Answer
Answer B is correct because For Woodgrove Bank, the technical constraint is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met.
Incorrect Answers
Answer A is incorrect because Woodgrove Bank must satisfy this condition: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. This option is aimed at another design goal.
Answer C is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. Woodgrove Bank needs a different capability; the required result is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Answer D is incorrect because The archive tier has the lowest storage cost for long-lived block blobs but data is offline and must be rehydrated before it can be read or modified. The Woodgrove Bank scenario instead calls for this outcome: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Question 11
Proseware wants rule-based storage-cost optimization that evaluates blob age and performs tiering actions automatically. What should it use? Choose ONE.
- Enable blob versioning
- Enable blob soft delete
- Configure an Azure Blob lifecycle management policy
- Use the archive access tier
Correct Answer: C
Correct Answer
Answer C is correct because The Proseware scenario turns on this requirement: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met. That makes this the appropriate choice.
Incorrect Answers
Answer A is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. The mismatch for Proseware is the stated requirement: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Answer B is incorrect because The Proseware design calls for this outcome: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This choice addresses another concern.
Answer D is incorrect because The archive tier has the lowest storage cost for long-lived block blobs but data is offline and must be rehydrated before it can be read or modified. That feature is valid Azure functionality, but The requirement for Proseware is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Question 12
Litware needs a declarative policy that removes old snapshots and moves older blob data to lower-cost tiers. Which feature should be configured? Choose ONE.
- Enable blob versioning
- Enable blob soft delete
- Use the archive access tier
- Configure an Azure Blob lifecycle management policy
Correct Answer: D
Correct Answer
Answer D is correct because Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met. The capability is relevant to Litware because the required outcome is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Incorrect Answers
Answer A is incorrect because In the Litware case, the required result is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. Selecting this would solve a neighboring problem instead.
Answer B is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. It is not the appropriate selection for Litware; the scenario requires: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions.
Answer C is incorrect because For Litware, the deciding constraint is: eligible blobs must automatically transition or expire according to age or other lifecycle rule conditions. The archive tier has the lowest storage cost for long-lived block blobs but data is offline and must be rehydrated before it can be read or modified. This solves a different operational need.
Question 13
Wingtip Toys wants each overwrite of an important block blob to preserve the prior state with a version identifier. Which feature should it enable? Choose ONE.
- Enable blob versioning
- Enable blob soft delete
- Create an Azure Files share snapshot
- Enable container soft delete
Correct Answer: A
Correct Answer
Answer A is correct because The scenario for Wingtip Toys requires this result: previous block-blob states must be preserved automatically when the current blob is modified or deleted. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. This directly addresses it.
Incorrect Answers
Answer B is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. That does not line up with the stated constraint for Wingtip Toys: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Answer C is incorrect because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. For Wingtip Toys, however, that does not meet the stated requirement: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Answer D is incorrect because Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. It misses the key condition in the Wingtip Toys case: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Question 14
- Datum needs to browse earlier states of a blob after multiple writes without requiring an administrator to create a snapshot before every change. What should it configure? Choose ONE.
- Enable blob soft delete
- Enable blob versioning
- Create an Azure Files share snapshot
- Enable container soft delete
Correct Answer: B
Correct Answer
Answer B is correct because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. It is the suitable choice for A. Datum; the deciding requirement is: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Incorrect Answers
Answer A is incorrect because The A. Datum scenario is testing this requirement: previous block-blob states must be preserved automatically when the current blob is modified or deleted. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This option does not provide that result.
Answer C is incorrect because The required outcome for A. Datum is: previous block-blob states must be preserved automatically when the current blob is modified or deleted. A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. This capability does not satisfy that condition.
Answer D is incorrect because The requirement for A. Datum is: previous block-blob states must be preserved automatically when the current blob is modified or deleted. Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. The option therefore targets a different Azure capability.
Question 15
Fourth Coffee wants automatic historical copies when a block blob is modified so an older state can later be promoted. Which feature is appropriate? Choose ONE.
- Enable blob soft delete
- Create an Azure Files share snapshot
- Enable blob versioning
- Enable container soft delete
Correct Answer: C
Correct Answer
Answer C is correct because For Fourth Coffee, the required behavior is: previous block-blob states must be preserved automatically when the current blob is modified or deleted. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. That is why this option fits.
Incorrect Answers
Answer A is incorrect because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. Fourth Coffee needs a different capability; the required result is: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Answer B is incorrect because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. The Fourth Coffee scenario instead calls for this outcome: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Answer D is incorrect because Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. This would not resolve the stated requirement for Fourth Coffee: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Question 16
Lucerne Publishing needs previous blob states to remain addressable after updates. Which Blob Storage data-protection option should it enable? Choose ONE.
- Enable blob soft delete
- Create an Azure Files share snapshot
- Enable container soft delete
- Enable blob versioning
Correct Answer: D
Correct Answer
Answer D is correct because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. The technical fit for Lucerne Publishing is direct because the requirement is: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Incorrect Answers
Answer A is incorrect because The Lucerne Publishing design calls for this outcome: previous block-blob states must be preserved automatically when the current blob is modified or deleted. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. This choice addresses another concern.
Answer B is incorrect because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. That feature is valid Azure functionality, but The requirement for Lucerne Publishing is: previous block-blob states must be preserved automatically when the current blob is modified or deleted.
Answer C is incorrect because For Lucerne Publishing, the required behavior is: previous block-blob states must be preserved automatically when the current blob is modified or deleted. Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. That is not the behavior this scenario calls for.
Question 17
Contoso wants protection against accidental deletion of both individual blobs and entire blob containers. Which TWO features should it enable? Choose TWO.
- Enable blob soft delete
- Enable blob versioning
- Enable container soft delete
- Create an Azure Files share snapshot
- Configure an Azure Blob lifecycle management policy
Correct Answers: A, C
Correct Answers
Answer A is correct because Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. For Contoso, that directly matches the stated requirement: blob soft delete protects deleted blobs while container soft delete protects deletion of a container and its contents.
Answer C is correct because For Contoso, the technical constraint is: blob soft delete protects deleted blobs while container soft delete protects deletion of a container and its contents. Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs.
Incorrect Answers
Answer B is incorrect because For Contoso, the deciding constraint is: blob soft delete protects deleted blobs while container soft delete protects deletion of a container and its contents. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. This solves a different operational need.
Answer D is incorrect because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. Even though the feature can be useful, it does not provide The required outcome for Contoso: blob soft delete protects deleted blobs while container soft delete protects deletion of a container and its contents.
Answer E is incorrect because The Contoso scenario is testing this requirement: blob soft delete protects deleted blobs while container soft delete protects deletion of a container and its contents. Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met. This option does not provide that result.
Question 18
Fabrikam wants to preserve previous blob states automatically and then use policies to tier or delete old versions. Which TWO features should it configure? Choose TWO.
- Enable container soft delete
- Enable blob versioning
- Enable soft delete for Azure file shares
- Configure an Azure Blob lifecycle management policy
- Create an Azure Files share snapshot
Correct Answers: B, D
Correct Answers
Answer B is correct because The required outcome for Fabrikam is: versioning creates previous blob versions and lifecycle management can act on eligible old versions. Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. This option provides that capability.
Answer D is correct because The Fabrikam scenario turns on this requirement: versioning creates previous blob versions and lifecycle management can act on eligible old versions. Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met. That makes this the appropriate choice.
Incorrect Answers
Answer A is incorrect because Container soft delete protects a deleted blob container and its contents for the configured retention period, addressing accidental deletion at the container level rather than only individual blobs. It misses the key condition in the Fabrikam case: versioning creates previous blob versions and lifecycle management can act on eligible old versions.
Answer C is incorrect because Fabrikam must satisfy this condition: versioning creates previous blob versions and lifecycle management can act on eligible old versions. Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. This option is aimed at another design goal.
Answer E is incorrect because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. Fabrikam needs a different capability; the required result is: versioning creates previous blob versions and lifecycle management can act on eligible old versions.
Question 19
Northwind Traders needs Azure Files protection for accidental share deletion and a point-in-time recovery copy before a major application change. Which TWO features should it use? Choose TWO.
- Enable soft delete for Azure file shares
- Enable blob soft delete
- Enable blob versioning
- Create an Azure Files share snapshot
- Create a Blob Storage container
Correct Answers: A, D
Correct Answers
Answer A is correct because Azure Files soft delete retains a deleted file share for the configured retention period so the share and its data can be recovered after accidental share deletion. The deciding condition in The Northwind Traders scenario is: file share soft delete protects a deleted share and a share snapshot captures a read-only point-in-time copy. This option fits that condition.
Answer D is correct because A file share snapshot is a read-only point-in-time copy of an Azure file share that supports recovery of individual files or broader share content after unwanted changes. The capability is relevant to Northwind Traders because the required outcome is: file share soft delete protects a deleted share and a share snapshot captures a read-only point-in-time copy.
Incorrect Answers
Answer B is incorrect because The requirement for Northwind Traders is: file share soft delete protects a deleted share and a share snapshot captures a read-only point-in-time copy. Blob soft delete retains deleted blobs and supported deleted snapshots or versions for a configured retention period so they can be recovered before permanent deletion. The option therefore targets a different Azure capability.
Answer C is incorrect because Blob versioning automatically preserves previous versions when a block blob is modified or deleted, allowing earlier states to remain addressable by version ID. The mismatch for Northwind Traders is the stated requirement: file share soft delete protects a deleted share and a share snapshot captures a read-only point-in-time copy.
Answer E is incorrect because The Northwind Traders design calls for this outcome: file share soft delete protects a deleted share and a share snapshot captures a read-only point-in-time copy. A blob container groups blobs within a storage account and is the data-plane boundary used to organize Blob Storage objects and apply container-level settings. This choice addresses another concern.
Question 20
Adventure Works stores active web assets and long-term compliance records in Blob Storage. Which TWO tier choices best fit the two usage patterns? Choose TWO.
- Use the cool access tier
- Use the hot access tier
- Use the cold access tier
- Configure an Azure Blob lifecycle management policy
- Use the archive access tier
Correct Answers: B, E
Correct Answers
Answer B is correct because The key requirement for Adventure Works is: frequently accessed assets belong in hot storage while rarely retrieved long-term records can use archive storage. The hot tier is optimized for data that is accessed or modified frequently and trades higher storage cost for lower access and transaction costs.
Answer E is correct because The scenario for Adventure Works requires this result: frequently accessed assets belong in hot storage while rarely retrieved long-term records can use archive storage. The archive tier has the lowest storage cost for long-lived block blobs but data is offline and must be rehydrated before it can be read or modified. This directly addresses it.
Incorrect Answers
Answer A is incorrect because The cool tier is intended for infrequently accessed data that still needs immediate online access, with lower capacity cost and higher access charges than hot storage. This would not resolve the stated requirement for Adventure Works: frequently accessed assets belong in hot storage while rarely retrieved long-term records can use archive storage.
Answer C is incorrect because In the Adventure Works case, the required result is: frequently accessed assets belong in hot storage while rarely retrieved long-term records can use archive storage. The cold tier is an online tier for rarely accessed data that still requires immediate retrieval, offering lower capacity cost than cool with higher access charges and a longer minimum retention period. Selecting this would solve a neighboring problem instead.
Answer D is incorrect because Lifecycle management applies rule-based actions to eligible blob data, such as moving blobs to cooler tiers or deleting old base blobs, versions, or snapshots when conditions are met. It is not the appropriate selection for Adventure Works; the scenario requires: frequently accessed assets belong in hot storage while rarely retrieved long-term records can use archive storage.
