1Y0-370 · Question #28
Scenario: A Citrix Engineer needs to restore files to an on-premise StorageZone deployment. The engineer has already initiated the file recovery on the ShareFile account. What is the next step the…
The correct answer is B. Retrieve file GUIDs to be restored with Get-RecoveryPendingFileIDs. See the full explanation below for the reasoning.
Question
Scenario: A Citrix Engineer needs to restore files to an on-premise StorageZone deployment. The engineer has already initiated the file recovery on the ShareFile account. What is the next step the engineer needs to take on the StorageZone Controller?
Options
- AComplete file recovery from the Configuration page.
- BRetrieve file GUIDs to be restored with Get-RecoveryPendingFileIDs.
- CRestore corresponding files from the backup location to the "staging" area.
- DRun DoRecovery.ps1 to process the queue that moves the files back to the persistent storage
How the community answered
(41 responses)- A15% (6)
- B73% (30)
- C7% (3)
- D5% (2)
Community Discussion
4
Viktor S.Jan 7, 2026The recovery process for on-premise StorageZones is a two-phase handshake between the ShareFile cloud side and your local Controller, and people fail this question because they jump to running scripts before the Controller even knows what to recover. Once you initiate recovery in the ShareFile account, the system queues up file GUIDs on the backend, but your StorageZone Controller has no idea which specific files are in scope until you pull that list with Get-RecoveryPendingFileIDs. That PowerShell cmdlet is the bridge, it gives your Controller the actual identifiers it needs to locate and process the right files. Without that step first, you are flying blind, and running DoRecovery.ps1 prematurely or going to the Configuration page does nothing useful because the Controller still does not know what it is supposed to recover. Correct answer is B. The workflow is sequential on purpose: initiate on the ShareFile side, retrieve the pending GUIDs with Get-RecoveryPendingFileIDs, then you move forward with the actual restoration steps. The other options are not wrong in a vacuum, they are just out of order, and order matters here.
Anjali D.Dec 24, 2025I kept gravitating toward D because running a recovery script feels like the obvious "next step" after initiating recovery on the ShareFile side, but then I remembered that the controller has to know which specific files to act on before any script can do anything useful, and that is exactly what Get-RecoveryPendingFileIDs gives you, the GUIDs that identify the pending items. Would love to hear if anyone else got tripped up by D, or if C seemed plausible because of the staging area mention.
Thekla S.Dec 25, 2025Exactly right on the sequencing logic, and I would add that from a least-privilege standpoint the GUID enumeration step also matters because it bounds the recovery scope before any elevated operation touches the file store, which is the kind of precision you want when a controller is acting on behalf of pending items rather than sweeping broadly.
Thekla S.Jan 12, 2026B is right, Get-RecoveryPendingFileIDs pulls the exact GUIDs queued for restore.