Request
Create maintenance-data in the supplied worker’s Availability Domain. Keep 200 GB after expansion, finish at 10 VPUs per GB, and retain the detached read-only record before the new read-write attachment.
Completion
Preserve both attachment histories and name the guest, filesystem and data evidence required in production.
A fictional digitization team needs a reviewable storage-maintenance sequence for a supplied worker. Declare its local volume, expand the capacity, attach it read-only for review and then detach that attachment. Preserve the expanded capacity while returning to the assigned performance setting, then declare a new read-write attachment.
Each step carries the earlier account, including both attachment records. Generated identifiers are stable training references, and real work must use actual returned OCIDs. The browser doesn't mount a filesystem or verify data on a device. End by naming the guest, application and consistency checks still needed. Report the old detached record and the new attachment independently so one doesn't conceal the other.