You save $69.98
An Azure administrator describes a solution for: select a redundancy option that survives a zone outage within the same region. What remaining limitation must not be misrepresented?
ZRS does not provide cross-region disaster recovery; region-wide outages require another protection strategy. That remains a practical service boundary even after the recommended change (choose zone-redundant storage (ZRS) when the account type and region support it) is implemented; retest it when identities, policies, service capacity or network paths change.
The incident (the app's LRS data becomes inaccessible during a zone-level storage failure) could recur if a related Azure dependency changes. The design still faces the limitation: ZRS does not provide cross-region disaster recovery; region-wide outages require another protection strategy.
The successful check 'Validate app reconnection and operational behavior during documented zonal-failure handling' proves only the tested behavior and cannot eliminate every dependent failure. The specific remaining limitation is: ZRS does not provide cross-region disaster recovery; region-wide outages require another protection strategy.
The two checks cover separate behavior: 'Validate app reconnection and operational behavior during documented zonal-failure handling' and 'Inspect account redundancy and confirm the intended ZRS SKU is applied'. Neither check removes the remaining operational limitation: ZRS does not provide cross-region disaster recovery; region-wide outages require another protection strategy.
A cloud administrator receives this request: A storage administrator needs to transfer several terabytes of blobs between accounts reliably using a scripted server job. The requirement is: perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility. Which configuration should be chosen first?
AzCopy is intended for high-throughput scripted transfer and provides status and retry behavior for Azure Storage operations. This achieves perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility through use AzCopy with appropriately scoped authorization and the correct source/destination URLs instead of relying on merely similar resource settings.
A query reads telemetry rather than performing bulk storage transfers; that would not meet perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility, for which the relevant Azure action is use AzCopy with appropriately scoped authorization and the correct source/destination URLs.
Account naming does not move blob contents; that would not meet perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility, for which the relevant Azure action is use AzCopy with appropriately scoped authorization and the correct source/destination URLs.
An exemption affects governance evaluation, not object copies; that would not meet perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility, for which the relevant Azure action is use AzCopy with appropriately scoped authorization and the correct source/destination URLs.
A pilot in Azure exposes this failure: A scheduled copy process completes without errors but the target contains only a subset of intended objects. The service was intended to meet: perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility. What is the most likely cause?
The trace reports: A scheduled copy process completes without errors but the target contains only a subset of intended objects. The causal misconfiguration is: The transfer command's source scope or filters omitted some blobs from the requested data set. The targeted action is to correct the AzCopy source/destination selection and rerun the missing transfer operations.
Required versioning, change feed, or the active object replication policy was not configured correctly; that mechanism would be more consistent with an observation such as new block blobs stop appearing at the destination despite an intended object replication rule, rather than this case's a scheduled copy process completes without errors but the target contains only a subset of intended objects.
The account uses GRS rather than a read-access geo-redundant configuration; that mechanism would be more consistent with an observation such as the application cannot read from the secondary endpoint before failover even though geo-replication is configured, rather than this case's a scheduled copy process completes without errors but the target contains only a subset of intended objects.
The selected redundancy keeps copies in one local fault domain instead of independent zones; that mechanism would be more consistent with an observation such as the app's LRS data becomes inaccessible during a zone-level storage failure, rather than this case's a scheduled copy process completes without errors but the target contains only a subset of intended objects.
The team confirms the following Azure defect: A scheduled copy process completes without errors but the target contains only a subset of intended objects. Which targeted remediation addresses the root cause?
Correct the AzCopy source/destination selection and rerun the missing transfer operations. This addresses the documented failure condition: the transfer command's source scope or filters omitted some blobs from the requested data set. Retest the affected operation and retain the original least-privilege boundaries.
A query reads telemetry rather than performing bulk storage transfers. In the reported incident (a scheduled copy process completes without errors but the target contains only a subset of intended objects), that change would not correct the cause: the transfer command's source scope or filters omitted some blobs from the requested data set.
An exemption affects governance evaluation, not object copies. In the reported incident (a scheduled copy process completes without errors but the target contains only a subset of intended objects), that change would not correct the cause: the transfer command's source scope or filters omitted some blobs from the requested data set.
Account naming does not move blob contents. In the reported incident (a scheduled copy process completes without errors but the target contains only a subset of intended objects), that change would not correct the cause: the transfer command's source scope or filters omitted some blobs from the requested data set.
A team has configured Azure for this workload: A storage administrator needs to transfer several terabytes of blobs between accounts reliably using a scripted server job. The requirement is: perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility. Which TWO verification steps would establish the relevant behavior? Select TWO answers.
Compare source and destination object counts and selected content hashes. This supplies observed evidence for perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility. It is not interchangeable with the second required check, restart an interrupted transfer and confirm its completed copies are handled predictably, because that checks a separate success or failure boundary.
Restart an interrupted transfer and confirm its completed copies are handled predictably. This supplies observed evidence for perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility. It is not interchangeable with the second required check, compare source and destination object counts and selected content hashes, because that checks a separate success or failure boundary.
A configured resource is not proof of live behavior. The required check must exercise compare source and destination object counts and selected content hashes on the affected Azure deployment.
A privileged administrator in a different subscription may succeed at 'Compare source and destination object counts and selected content hashes' even though the intended caller fails. This does not prove the required behavior for compare source and destination object counts and selected content hashes.
A release checklist recording 'Restart an interrupted transfer and confirm its completed copies are handled predictably' is not evidence that the required operation actually succeeded or failed. To establish the correct result, the team must restart an interrupted transfer and confirm its completed copies are handled predictably on the actual workload to prove its independent boundary.
A risk reviewer is considering an Azure design that aims to: perform scalable server-side bulk blob copies using a supported Microsoft Azure transfer utility. Which limitation should still be documented?
AzCopy throughput depends on network, throttling and credentials; successful transfer is not proof that access policies were preserved. That remains a practical service boundary even after the recommended change (use AzCopy with appropriately scoped authorization and the correct source/destination URLs) is implemented; retest it when identities, policies, service capacity or network paths change.
The successful check 'Compare source and destination object counts and selected content hashes' proves only the tested behavior and cannot eliminate every dependent failure. The specific remaining limitation is: AzCopy throughput depends on network, throttling and credentials; successful transfer is not proof that access policies were preserved.
The two checks cover separate behavior: 'Compare source and destination object counts and selected content hashes' and 'Restart an interrupted transfer and confirm its completed copies are handled predictably'. Neither check removes the remaining operational limitation: AzCopy throughput depends on network, throttling and credentials; successful transfer is not proof that access policies were preserved.
The incident (a scheduled copy process completes without errors but the target contains only a subset of intended objects) could recur if a related Azure dependency changes. The design still faces the limitation: AzCopy throughput depends on network, throttling and credentials; successful transfer is not proof that access policies were preserved.
An Azure administrator must resolve a specific request: A blob account contains monthly reports whose access frequency falls sharply after 45 days and should be deleted after a fixed approved retention period. The expected outcome is: automate movement to lower-access tiers and expiry based on object age. Which option is appropriate?
Blob lifecycle rules can transition eligible objects and delete old versions or blobs according to configured conditions. This achieves automate movement to lower-access tiers and expiry based on object age through create a lifecycle management policy with the required filters and age-based tier/delete actions instead of relying on merely similar resource settings.
Network endpoints do not control object lifecycle; that would not meet automate movement to lower-access tiers and expiry based on object age, for which the relevant Azure action is create a lifecycle management policy with the required filters and age-based tier/delete actions.
Reader authorizes access but does not create aging actions; that would not meet automate movement to lower-access tiers and expiry based on object age, for which the relevant Azure action is create a lifecycle management policy with the required filters and age-based tier/delete actions.
Manual untracked tiering cannot reliably implement a repeatable schedule; that would not meet automate movement to lower-access tiers and expiry based on object age, for which the relevant Azure action is create a lifecycle management policy with the required filters and age-based tier/delete actions.
Operations sees an unexpected outcome: Reports remain in Hot storage long after they should transition to Cool. The original demand was: automate movement to lower-access tiers and expiry based on object age. Which cause is most consistent with the evidence?
The trace reports: Reports remain in Hot storage long after they should transition to Cool. The causal misconfiguration is: The lifecycle policy was missing, had incorrect filters, or was not targeting the intended objects. The targeted action is to correct the policy prefix filter and last-modified age conditions for eligible blobs.
Archive is an offline tier and its objects were not rehydrated for interactive reads; that mechanism would be more consistent with an observation such as analysts cannot read annual files immediately after an archive-tier move, rather than this case's reports remain in Hot storage long after they should transition to Cool.
Blob versioning was not enabled or historical versions were deleted by lifecycle rules; that mechanism would be more consistent with an observation such as an overwritten object no longer has the earlier accepted bytes available, rather than this case's reports remain in Hot storage long after they should transition to Cool.
The object is outside the configured retention window or soft delete was not enabled before deletion; that mechanism would be more consistent with an observation such as the deleted blob cannot be recovered because its soft-delete retention expired, rather than this case's reports remain in Hot storage long after they should transition to Cool.
A service owner needs a practical fix after this failure: Reports remain in Hot storage long after they should transition to Cool. What is the best remediation?
Correct the policy prefix filter and last-modified age conditions for eligible blobs. This addresses the documented failure condition: the lifecycle policy was missing, had incorrect filters, or was not targeting the intended objects. Retest the affected operation and retain the original least-privilege boundaries.
Reader authorizes access but does not create aging actions. In the reported incident (reports remain in Hot storage long after they should transition to Cool), that change would not correct the cause: the lifecycle policy was missing, had incorrect filters, or was not targeting the intended objects.
Manual untracked tiering cannot reliably implement a repeatable schedule. In the reported incident (reports remain in Hot storage long after they should transition to Cool), that change would not correct the cause: the lifecycle policy was missing, had incorrect filters, or was not targeting the intended objects.
Network endpoints do not control object lifecycle. In the reported incident (reports remain in Hot storage long after they should transition to Cool), that change would not correct the cause: the lifecycle policy was missing, had incorrect filters, or was not targeting the intended objects.
A deployment claims to meet: automate movement to lower-access tiers and expiry based on object age. The environment is: A blob account contains monthly reports whose access frequency falls sharply after 45 days and should be deleted after a fixed approved retention period. Which TWO test results would substantiate that claim? Select TWO answers.
Inspect a test object that crosses the transition threshold and confirm its target tier. This supplies observed evidence for automate movement to lower-access tiers and expiry based on object age. It is not interchangeable with the second required check, verify an excluded or legally retained object is not unintentionally deleted, because that checks a separate success or failure boundary.
Verify an excluded or legally retained object is not unintentionally deleted. This supplies observed evidence for automate movement to lower-access tiers and expiry based on object age. It is not interchangeable with the second required check, inspect a test object that crosses the transition threshold and confirm its target tier, because that checks a separate success or failure boundary.
A privileged administrator in a different subscription may succeed at 'Inspect a test object that crosses the transition threshold and confirm its target tier' even though the intended caller fails. This does not prove the required behavior for inspect a test object that crosses the transition threshold and confirm its target tier.
A release checklist recording 'Verify an excluded or legally retained object is not unintentionally deleted' is not evidence that the required operation actually succeeded or failed. To establish the correct result, the team must verify an excluded or legally retained object is not unintentionally deleted on the actual workload to prove its independent boundary.
A configured resource is not proof of live behavior. The relevant result must be observed by inspecting a test object that crosses the transition threshold and confirm its target tier on the affected Azure deployment.
An infrastructure design was selected to meet: automate movement to lower-access tiers and expiry based on object age. What caveat remains relevant during operation?
Lifecycle evaluation is asynchronous, and deletion rules must account for versioning, legal hold and immutable retention. That remains a practical service boundary even after the recommended change (create a lifecycle management policy with the required filters and age-based tier/delete actions) is implemented; retest it when identities, policies, service capacity or network paths change.
The two checks cover separate behavior: 'Inspect a test object that crosses the transition threshold and confirm its target tier' and 'Verify an excluded or legally retained object is not unintentionally deleted'. Neither check removes the remaining operational limitation: Lifecycle evaluation is asynchronous, and deletion rules must account for versioning, legal hold and immutable retention.
The incident (reports remain in Hot storage long after they should transition to Cool) could recur if a related Azure dependency changes. The design still faces the limitation: Lifecycle evaluation is asynchronous, and deletion rules must account for versioning, legal hold and immutable retention.
The successful check 'Inspect a test object that crosses the transition threshold and confirm its target tier' proves only the tested behavior and cannot eliminate every dependent failure. The specific remaining limitation is: Lifecycle evaluation is asynchronous, and deletion rules must account for versioning, legal hold and immutable retention.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (606 Questions, Last Updated on Oct 25, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
