Verifying cloud backup recoverability | LinuC Level 1 102 Exam original practice question

1.10.4Basic

Back up cloud data and confirm that it can be restored after a failure.

Which backup practice is appropriate?

Hint 1: Focus on the responsibility boundary

Separate account, network, storage, audit, and recovery controls before comparing the choices.

Hint 2: Key terms

Review the short definitions of cloud security boundaries, authentication factors, permissions, and recovery controls involved.

Restore test: A test that actually recovers data or a workload from a backup.
Retention: The period or number of generations for which backups are kept.
Failure-domain separation: Keeping copies in an independent location or infrastructure boundary.
Access control: Rules that limit who can read, change, or delete backup data.

Detailed explanation

Incorrect一度取得したら復元テストをしない。

Incorrect. Without restore tests, corruption or permission failures may remain hidden.

Correct取得成功だけでなく、復元テスト、保持期間、アクセス制御、別障害領域への複製を確認する。

Correct. A successful backup job is not enough; restore and protection must also be verified.

Incorrect本番と同じ単一ディスクだけに保存する。

Incorrect. A single disk in the same failure domain can lose the source and backup together.

Incorrect誰でも削除できる共有バケットへ置く。

Incorrect. A bucket anyone can delete is vulnerable to accidental deletion and leakage.

An example you can run in a temporary verification environment.

printf '%s\n' 'backup success is not recovery proof until restore is tested'

backup success is not recovery proof until restore is tested

Foundation review

Define how much data may be lost and how quickly the service must be restored.

Check protection for backups both while stored and while transferred.

Question IDKL-102-1177

Environmentクラウドバックアップ運用の概念確認

Last technical review2026-08-20

More practice in this area