Chapter 32 - Worked Answers

1. Three storage identities

Claim name selects a namespace-local logical claim; VolumeID identifies metadata; VolumeName is what the agent forwards to Docker’s name:target:mode bind. The current mapping does not add namespace or UUID to that physical name. Equal names in different logical namespaces on one daemon can therefore collide, despite scoped metadata. Use a unique run-owned name and actual mount inspection for live tests; do not infer physical storage isolation from secret-reference tests.

2. Conservative active attachment rule

For a new writable RWO mount without concurrent-writer permission, the helper rejects if any active attachment has the same VolumeID. It does not filter existing attachments by ReadOnly. A new reader skips the writable branch, but an existing reader can block a later writer. This qualifies the documentation’s simpler readers-do-not-consume-lock statement. allow_concurrent_writers bypasses that branch without implementing application-level safe concurrent writes.

3. Logical lock versus lost node

The test proves one accepted metadata writer and later detached records under injected reports. A lost heartbeat does not prove the old host process stopped, and another host does not automatically possess the local volume’s bytes. Metadata RWO is not distributed fencing, replication or backup. Safe failover requires actual revocation/process evidence and an explicit data recovery/migration plan outside the present MVP.

4. Retention and stale binding

Create an exact owned named volume with harmless sentinel data, replace only its run-owned container on the same node and inspect the same mount/data. State whether final cleanup retains or deletes that exact volume; never broad-prune. Separately capture a resolved mount before its first binding, bind the volume, then attempt later placement using the old snapshot. Assert latest topology is enforced or document failure. The helper checks mount.NodeID, so copied stale snapshots need explicit coverage before claiming every retry remains pinned.

These answers use chapter 32 and its scoped claim/execution records. Design changes remain proposals until separately implemented and tested.