SY0-701 Security Operations Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Increase the retention period so the backup console will keep more copies.

  Why it's wrong here

  Increasing the retention period only dictates how long older backup sets are retained in the repository; it has no effect on the authentication process that occurs when the backup application connects to the storage or encryption service. Restore failed because the service account or encryption credentials are no longer valid, not because there are too few copies available. Even with hundreds of retained backups, a restore will still fail if the restore engine cannot authenticate to the backup data, so retention changes are irrelevant to this symptom.

• ✓

  Update the backup application with the current service account credentials and rerun a restore validation test.

  Why this is correct

  The backup job may complete successfully using cached, per-job credentials, while the restore operation uses a separate service account whose password was rotated or whose legacy authentication settings were revoked. Updating the backup application with the current service account credentials eliminates the credential mismatch and ensures that the restore process can read the encrypted backup data. Rerunning a restore validation test is essential because 'backup success' is meaningless if the organization cannot actually recover data during a disaster.

• ✗

  Disable the backup software firewall rule and try the restore again later.

  Why it's wrong here

  An authentication failure, typically signified by HTTP 401, 'Access Denied', or 'Invalid password', indicates that the identity presented by the backup application was rejected, which is a credential problem, not a communication problem. Firewall rules control network flow (ports, IPs, protocols) and cannot cause an account to fail password verification; if the firewall were blocking traffic, the error would be a timeout or 'connection refused'. Disabling the backup software's firewall rule would not fix the authentication error and would expose the backup infrastructure to unnecessary attack surface, making it the wrong remedy.

• ✗

  Delete and recreate all protected files because the backup repository is probably corrupt.

  Why it's wrong here

  Deleting and recreating all protected files would destroy the source data while doing nothing to address the authentication failure that occurs when the restore process tries to access the backup repository. Repository corruption typically manifests as checksum mismatches, I/O errors, or a backup console warning, not as an authentication failure during restore. Before taking such a destructive action, the correct approach would be to verify the backup repository with vendor integrity checks, test an alternate restore point, or validate the service account permissions — not blindly delete data.

Go deeper

Related to this question