Question 450
Original unofficial HPE0-J83 storage practice case R183-CASE-113 — Data center adopts Infrastructure as Code. Observed evidence: Storage volume definitions are pushed without drift reconciliation and override manual RBAC. After the scoped corrective action, which observation most directly demonstrates that this issue is resolved?
Explanation
Correct Answer
The acceptance result Repeat deployment yields no unintended volume or privilege changes directly tests recovery for this situation: Automation ignores idempotency and approval controls. The prior signal was: Storage volume definitions are pushed without drift reconciliation and override manual RBAC. The planned intervention was: Apply declarative storage templates with role checks and drift review. This targeted evidence is more useful than merely reporting that an array is online.
Incorrect Answers
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Encryption lifecycle and backup key provenance are not coordinated, signaled by: Key-rotation runbook changes keys without verifying recovery of older backups. The current symptom is: Storage volume definitions are pushed without drift reconciliation and override manual RBAC. Verify this incident by checking: Repeat deployment yields no unintended volume or privilege changes.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Cloud delivery model lacks resource isolation and independent access audit, signaled by: All customers share an unrestricted storage management account. The current symptom is: Storage volume definitions are pushed without drift reconciliation and override manual RBAC. Verify this incident by checking: Repeat deployment yields no unintended volume or privilege changes.
Incorrect for this case-specific acceptance test. That result would demonstrate progress against: Ransomware can delete both active and nominal backup copies, signaled by: Backup repository is accessible with the same admin credentials as production. The current symptom is: Storage volume definitions are pushed without drift reconciliation and override manual RBAC. Verify this incident by checking: Repeat deployment yields no unintended volume or privilege changes.