Microsoft AZ-800 Practice Test 69 - Prepaway
Practice Exams:

Pass Microsoft AZ-800 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

AZ-800 Premium Bundle


  • Premium File 311 Questions & Answers. Last update: Nov 12, 2026
  • Training Course 150 Lectures
  • Study Guide 430 Pages

Microsoft AZ-800 Practice Test 69

Question 680

At Northgate Storage Resilience, the team supports Storage Spaces and replication between Windows servers and must meet documented data durability and recovery conditions. The original incident is: A branch file server continues accepting local edits but none of the changes appear in the cloud endpoint. The evidence is: File Sync health telemetry reports the server endpoint offline because the agent cannot reach the approved service. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Restore the supported sync agent and required service endpoints, then reconcile pending files and sync health. Evidence of success: A new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict.
  2. Action: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Evidence of success: The server maintains the approved free-space headroom while requested files rehydrate on demand.
  3. Action: Apply the documented sync conflict recovery and file ownership workflow using preserved versions rather than deleting conflicts blindly. Evidence of success: Both intended changes are reconciled in an approved final document with preserved audit evidence.
  4. Action: Size and locate supported Replica log volumes and bandwidth to observed write-change rate with controlled resynchronization. Evidence of success: Replication backlog stays within target during representative load and a controlled failover verifies consistent data.

Explanation

Correct Answer

A:

This proposed change-and-check pair is tied to the Northgate Storage Resilience fault: Action: Restore the supported sync agent and required service endpoints, then reconcile pending files and sync health. Evidence of success: A new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict. The diagnostic basis is that file Sync health telemetry reports the server endpoint offline because the agent cannot reach the approved service. The outcome must show that a new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict.

Incorrect Answers

B:

The paired proposal is Action: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Evidence of success: The server maintains the approved free-space headroom while requested files rehydrate on demand. For Northgate Storage Resilience, it fails to establish an intervention and check for the documented issue, where a branch file server continues accepting local edits but none of the changes appear in the cloud endpoint. Successful closure requires that a new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict.

C:

At Northgate Storage Resilience, the option couples action: Apply the documented sync conflict recovery and file ownership workflow using preserved versions rather than deleting conflicts blindly. Evidence of success: Both intended changes are reconciled in an approved final document with preserved audit evidence. Its test does not independently demonstrate that a new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict. The deciding case evidence is that file Sync health telemetry reports the server endpoint offline because the agent cannot reach the approved service.

D:

This offered change and proof, action: Size and locate supported Replica log volumes and bandwidth to observed write-change rate with controlled resynchronization. Evidence of success: Replication backlog stays within target during representative load and a controlled failover verifies consistent data, would leave the Northgate Storage Resilience case unverified. The actual recorded fault is that a branch file server continues accepting local edits but none of the changes appear in the cloud endpoint. A meaningful check requires that a new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict.

Question 681

At Pinebrook Branch File Services, the team supports BranchCache and distributed document access and must reduce WAN demand without violating file authorization. Confirmed original fault: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Supporting diagnostic evidence: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Update the authorized DFS namespace target and verify file migration, referrals, access ACLs and client transition.
  2. Disable or remove the stale referral and configure target priority and site-aware referrals according to the approved namespace design.
  3. Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements.
  4. Recreate or migrate the volume to a supported capacity-appropriate resilient layout after preserving data and recovery plans.

Explanation

Correct Answer

C:

At Pinebrook Branch File Services, tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The fitting correction is to set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity. The acceptance check is that the server maintains the approved free-space headroom while requested files rehydrate on demand.

Incorrect Answers

A:

The failure at Pinebrook Branch File Services is that an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. That does not call for update the authorized DFS namespace target and verify file migration, referrals, access ACLs and client transition. The case evidence instead establishes that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.

B:

At Pinebrook Branch File Services, proposing to disable or remove the stale referral and configure target priority and site-aware referrals according to the approved namespace design would not address the recorded evidence: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The case instead needs an intervention related to an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

D:

Proposing to recreate or migrate the volume to a supported capacity-appropriate resilient layout after preserving data and recovery plans does not fit the evidence at Pinebrook Branch File Services: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. That would not resolve the original failure: an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled.

Question 682

At Pinebrook Branch File Services, the team supports BranchCache and distributed document access and must reduce WAN demand without violating file authorization. A reported incident states: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Before changing the environment, the team must distinguish among plausible technical causes. Which observation most decisively distinguishes this specific Windows Server failure from other problems?

  1. File Sync conflict files and timestamps reveal two divergent edits rather than a simple connectivity delay.
  2. Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.
  3. MPIO and iSCSI session inventory show a missing redundant session and asymmetric path policies versus the validated storage design.
  4. SMB multichannel counters show no active RDMA-capable channel while the link passes ordinary TCP SMB traffic.

Explanation

Correct Answer

B:

This observation is the appropriate evidence for Pinebrook Branch File Services: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. It explains the problem, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Incorrect Answers

A:

This observation, file Sync conflict files and timestamps reveal two divergent edits rather than a simple connectivity delay, does not match the evidence in the Pinebrook Branch File Services record. Instead, the record shows that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

C:

The observation offered is that mPIO and iSCSI session inventory show a missing redundant session and asymmetric path policies versus the validated storage design. It does not substantiate the reported Pinebrook Branch File Services failure, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The directly relevant diagnostic record is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.

D:

The suggested evidence is that sMB multichannel counters show no active RDMA-capable channel while the link passes ordinary TCP SMB traffic. In the Pinebrook Branch File Services case, the actual distinguishing finding is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Question 683

At Pinebrook Branch File Services, the team supports BranchCache and distributed document access and must reduce WAN demand without violating file authorization. Observed issue: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Investigation found: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The proposed repair is: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. The server maintains the approved free-space headroom while requested files rehydrate on demand.
  2. The documented upload succeeds within revised policy and a deliberate over-quota test is blocked and reported.
  3. A planned single-disk failure test maintains the documented availability target without losing files.
  4. The LUN remains reachable through a deliberate single-path interruption and file service checks pass.

Explanation

Correct Answer

A:

For Pinebrook Branch File Services, the offered check would demonstrate that the server maintains the approved free-space headroom while requested files rehydrate on demand. It evaluates the actual failure, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Incorrect Answers

B:

This check suggests that the documented upload succeeds within revised policy and a deliberate over-quota test is blocked and reported. It does not test the resolution criterion for Pinebrook Branch File Services, namely that the server maintains the approved free-space headroom while requested files rehydrate on demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

C:

The option would validate that a planned single-disk failure test maintains the documented availability target without losing files. That does not establish correction of the Pinebrook Branch File Services issue, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The meaningful proof is that the server maintains the approved free-space headroom while requested files rehydrate on demand.

D:

The alternative test result is that the LUN remains reachable through a deliberate single-path interruption and file service checks pass. It does not prove recovery of the Pinebrook Branch File Services failure, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. A relevant acceptance result would show that the server maintains the approved free-space headroom while requested files rehydrate on demand.

Question 684

At Pinebrook Branch File Services, the team supports BranchCache and distributed document access and must reduce WAN demand without violating file authorization. The administrator observes: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The distinguishing clue is: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?

  1. Azure Files identity-based SMB access can require both share-level role assignment and file-system ACL authorization.
  2. Effective Windows SMB access is constrained by the intersection of share and NTFS permissions.
  3. Storage Replica reliability depends on adequate change log performance and transport capacity for write rate.
  4. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Explanation

Correct Answer

D:

For Pinebrook Branch File Services, the governing principle is that cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity. The deciding observation is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. This directly explains the documented failure.

Incorrect Answers

A:

This offered mechanism, azure Files identity-based SMB access can require both share-level role assignment and file-system ACL authorization, does not match the specific recorded failure at Pinebrook Branch File Services, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The relevant principle is that cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

B:

At Pinebrook Branch File Services, the reported clue is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The principle of effective Windows SMB access is constrained by the intersection of share and NTFS permissions does not explain that finding. The appropriate explanation is that cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

C:

The alternate technical explanation says that storage Replica reliability depends on adequate change log performance and transport capacity for write rate. It is not the mechanism identified by the Pinebrook Branch File Services record: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Question 685

At Pinebrook Branch File Services, the team supports BranchCache and distributed document access and must reduce WAN demand without violating file authorization. The original incident is: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The evidence is: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Evidence of success: The server maintains the approved free-space headroom while requested files rehydrate on demand.
  2. Action: Restore the supported sync agent and required service endpoints, then reconcile pending files and sync health. Evidence of success: A new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict.
  3. Action: Disable or remove the stale referral and configure target priority and site-aware referrals according to the approved namespace design. Evidence of success: Clients resolve to healthy appropriate targets and domain namespace access survives the retired server being offline.
  4. Action: Issue or bind the trusted certificate for the approved SMB over QUIC server name and validate network access controls. Evidence of success: A remote authorized client mounts the share through the secured QUIC path and unapproved identities remain denied.

Explanation

Correct Answer

A:

At Pinebrook Branch File Services, the offered pair combines a relevant intervention with proof: Action: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Evidence of success: The server maintains the approved free-space headroom while requested files rehydrate on demand. It responds to the evidence that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. A successful result should establish that the server maintains the approved free-space headroom while requested files rehydrate on demand.

Incorrect Answers

B:

At Pinebrook Branch File Services, the option couples action: Restore the supported sync agent and required service endpoints, then reconcile pending files and sync health. Evidence of success: A new test file arrives on both endpoints and the pending sync queue drains without unresolved conflict. Its test does not independently demonstrate that the server maintains the approved free-space headroom while requested files rehydrate on demand. The deciding case evidence is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.

C:

This offered change and proof, action: Disable or remove the stale referral and configure target priority and site-aware referrals according to the approved namespace design. Evidence of success: Clients resolve to healthy appropriate targets and domain namespace access survives the retired server being offline, would leave the Pinebrook Branch File Services case unverified. The actual recorded fault is that an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. A meaningful check requires that the server maintains the approved free-space headroom while requested files rehydrate on demand.

D:

The alternative combined step is Action: Issue or bind the trusted certificate for the approved SMB over QUIC server name and validate network access controls. Evidence of success: A remote authorized client mounts the share through the secured QUIC path and unapproved identities remain denied. The relevant Pinebrook Branch File Services evidence is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Closure must validate that the server maintains the approved free-space headroom while requested files rehydrate on demand, rather than a different symptom.

Question 686

At Northgate Storage Resilience, the team supports Storage Spaces and replication between Windows servers and must meet documented data durability and recovery conditions. Confirmed original fault: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Supporting diagnostic evidence: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Restore the supported sync agent and required service endpoints, then reconcile pending files and sync health.
  2. Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements.
  3. Configure matching supported BranchCache mode and server content publication with approved security settings.
  4. Restore supported multipath and iSCSI initiator/target session bindings without duplicating the disk identity.

Explanation

Correct Answer

B:

At Northgate Storage Resilience, tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The fitting correction is to set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity. The acceptance check is that the server maintains the approved free-space headroom while requested files rehydrate on demand.

Incorrect Answers

A:

At Northgate Storage Resilience, proposing to restore the supported sync agent and required service endpoints, then reconcile pending files and sync health would not address the recorded evidence: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The case instead needs an intervention related to an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

C:

Proposing to configure matching supported BranchCache mode and server content publication with approved security settings does not fit the evidence at Northgate Storage Resilience: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. That would not resolve the original failure: an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled.

D:

The issue at Northgate Storage Resilience is that an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Acting to restore supported multipath and iSCSI initiator/target session bindings without duplicating the disk identity would not correct the evidenced cause. The most relevant clue is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.

Question 687

At Northgate Storage Resilience, the team supports Storage Spaces and replication between Windows servers and must meet documented data durability and recovery conditions. A reported incident states: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Before changing the environment, the team must distinguish among plausible technical causes. Which observation most decisively distinguishes this specific Windows Server failure from other problems?

  1. File Sync conflict files and timestamps reveal two divergent edits rather than a simple connectivity delay.
  2. Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.
  3. The share grants read access while the folder's NTFS discretionary ACL excludes the user's actual token.
  4. Client TLS diagnostics identify a certificate subject mismatch with the published SMB server name.

Explanation

Correct Answer

B:

At Northgate Storage Resilience, the selected observation is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. That evidence distinguishes the reported failure, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Incorrect Answers

A:

For Northgate Storage Resilience, the proposed observation is that file Sync conflict files and timestamps reveal two divergent edits rather than a simple connectivity delay. It would not distinguish the identified failure, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The meaningful clue is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.

C:

The suggested evidence is that the share grants read access while the folder's NTFS discretionary ACL excludes the user's actual token. In the Northgate Storage Resilience case, the actual distinguishing finding is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

D:

At Northgate Storage Resilience, The alternative observation about client TLS diagnostics identify a certificate subject mismatch with the published SMB server name would not isolate the relevant problem. The diagnostic clue is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. This is the clue that bears on an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled.

Question 688

At Northgate Storage Resilience, the team supports Storage Spaces and replication between Windows servers and must meet documented data durability and recovery conditions. Observed issue: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. Investigation found: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The proposed repair is: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. The server maintains the approved free-space headroom while requested files rehydrate on demand.
  2. The group member can read the approved folder and a nonmember remains denied despite seeing the share name.
  3. The LUN remains reachable through a deliberate single-path interruption and file service checks pass.
  4. A controlled file transfer uses an RDMA-capable SMB channel and meets expected latency without weakening authentication.

Explanation

Correct Answer

A:

The verification signal is that the server maintains the approved free-space headroom while requested files rehydrate on demand. It connects the proposed correction to the recorded diagnostic clue at Northgate Storage Resilience: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Incorrect Answers

B:

The option would validate that the group member can read the approved folder and a nonmember remains denied despite seeing the share name. That does not establish correction of the Northgate Storage Resilience issue, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The meaningful proof is that the server maintains the approved free-space headroom while requested files rehydrate on demand.

C:

The alternative test result is that the LUN remains reachable through a deliberate single-path interruption and file service checks pass. It does not prove recovery of the Northgate Storage Resilience failure, where an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. A relevant acceptance result would show that the server maintains the approved free-space headroom while requested files rehydrate on demand.

D:

The alternative validation would show that a controlled file transfer uses an RDMA-capable SMB channel and meets expected latency without weakening authentication. For Northgate Storage Resilience, that is insufficient to establish that the server maintains the approved free-space headroom while requested files rehydrate on demand. The original diagnostic finding is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand.

Question 689

At Northgate Storage Resilience, the team supports Storage Spaces and replication between Windows servers and must meet documented data durability and recovery conditions. The administrator observes: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The distinguishing clue is: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?

  1. Azure Files identity-based SMB access can require both share-level role assignment and file-system ACL authorization.
  2. Azure File Sync depends on healthy registered agents and service connectivity, not just a working local SMB share.
  3. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.
  4. DFS Namespaces provide logical paths but depend on healthy and correctly prioritized referral targets.

Explanation

Correct Answer

C:

For Northgate Storage Resilience, the governing principle is that cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity. The deciding observation is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. This directly explains the documented failure.

Incorrect Answers

A:

At Northgate Storage Resilience, the reported clue is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The principle of azure Files identity-based SMB access can require both share-level role assignment and file-system ACL authorization does not explain that finding. The appropriate explanation is that cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

B:

The alternate technical explanation says that azure File Sync depends on healthy registered agents and service connectivity, not just a working local SMB share. It is not the mechanism identified by the Northgate Storage Resilience record: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

D:

The alternative rule states that dFS Namespaces provide logical paths but depend on healthy and correctly prioritized referral targets. It does not account for the Northgate Storage Resilience evidence: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The case turns on the mechanism that cloud tiering cache behavior requires deliberate working-set and free-space management, not an assumption of infinite local capacity.

Question 690

At Northgate Storage Resilience, the team supports Storage Spaces and replication between Windows servers and must meet documented data durability and recovery conditions. The original incident is: An Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The evidence is: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Evidence of success: The server maintains the approved free-space headroom while requested files rehydrate on demand.
  2. Action: Assign the intended identity-based share role and NTFS permissions with least privilege on the authorized folder. Evidence of success: The intended user opens the folder while a nonmember with share visibility is denied by folder permissions.
  3. Action: Size and locate supported Replica log volumes and bandwidth to observed write-change rate with controlled resynchronization. Evidence of success: Replication backlog stays within target during representative load and a controlled failover verifies consistent data.
  4. Action: Restore supported multipath and iSCSI initiator/target session bindings without duplicating the disk identity. Evidence of success: The LUN remains reachable through a deliberate single-path interruption and file service checks pass.

Explanation

Correct Answer

A:

The documented issue at Northgate Storage Resilience is that an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. The selected combined action and test is Action: Set supported tiering and volume free-space policy using representative working-set demand and retrieval requirements. Evidence of success: The server maintains the approved free-space headroom while requested files rehydrate on demand. Its verification aligns with the required outcome: The server maintains the approved free-space headroom while requested files rehydrate on demand.

Incorrect Answers

B:

This offered change and proof, action: Assign the intended identity-based share role and NTFS permissions with least privilege on the authorized folder. Evidence of success: The intended user opens the folder while a nonmember with share visibility is denied by folder permissions, would leave the Northgate Storage Resilience case unverified. The actual recorded fault is that an Azure File Sync server endpoint runs out of free disk even though cloud tiering is enabled. A meaningful check requires that the server maintains the approved free-space headroom while requested files rehydrate on demand.

C:

The alternative combined step is Action: Size and locate supported Replica log volumes and bandwidth to observed write-change rate with controlled resynchronization. Evidence of success: Replication backlog stays within target during representative load and a controlled failover verifies consistent data. The relevant Northgate Storage Resilience evidence is that tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. Closure must validate that the server maintains the approved free-space headroom while requested files rehydrate on demand, rather than a different symptom.

D:

The paired remediation states Action: Restore supported multipath and iSCSI initiator/target session bindings without duplicating the disk identity. Evidence of success: The LUN remains reachable through a deliberate single-path interruption and file service checks pass. It does not test correction of the Northgate Storage Resilience condition: Tiering policy metadata shows the volume free-space target was not configured to release cold content under current cache demand. The outcome to verify is that the server maintains the approved free-space headroom while requested files rehydrate on demand.

Administering Windows Server Hybrid Core Infrastructure (AZ-800) Practice Tests