Easy ReviewDOP-C02
Configuration Management and IaC34

Backup

Schedule backups, protect recovery points, copy them across accounts and Regions, and test restores.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

AWS Backup manages backup plans and recovery points for supported AWS resources. These sections explain resource selection, organization policies, copy requirements, vault retention protection, and restore testing.

Plans, vaults, and recovery points

AWS Backup schedules and retains backups for assigned AWS resources. A plan is the timetable, a vaultA container that stores and organizes recovery points. is the storage container, and a recovery pointA saved backup that AWS Backup can use to restore a resource. is the saved backup you can restore.

How it works

  1. Create a plan with backup rules. Each rule sets the schedule, start windowThe period in which a scheduled backup job is allowed to begin., completion windowThe time allowed for a backup job to finish after it starts., destination vault, and lifecycleThe settings that determine when a backup changes storage tier and expires.. Lifecycle means when a backup changes storage tier or expires.
  2. Assign resources by type, tagsA key-value label used to select or describe a resource., or individual Amazon Resource Names (ARNs), which identify AWS resources. Tags are key-value labels.
  3. Choose snapshotsA backup of resource data as captured at a particular time. for the state captured by each backup, or continuous backups for point-in-time recoveryRestoring data to a chosen time within a continuous backup retention period. (PITR), which restores to a chosen time within the retention periodThe length of time a backup is kept before it expires..
  4. AWS Backup stores recovery points in the vault. For resource types that support incremental backupsA backup that saves changes since earlier backups after an initial full backup., it saves a full backup first and changes afterward. Other types use full backups.
Rule setting Meaning
Start window Time allowed for a job to begin
Completion window Time allowed for a started job to finish
Lifecycle Storage transition and deletion timing
Copy action Additional backup in a destination vault

Exam cues

  • If the question says two backup rule start windows overlap, think longer retention, because AWS Backup optimizes overlapping backups under that rule.
  • If the question says restore to a chosen time, think continuous backups, because snapshots only preserve captured states.

Remember

  • Continuous retention: 1 to 35 days.
  • Eligible cold backups must stay cold for at least 90 days. Schedule deletion at least 90 days after transition.
  • Backups come from plans or on demand. Most frequent schedule: hourly.

Trap: A vault key does not determine every backup’s encryption. Independently encrypted backups use it; other resources inherit source-service encryption.

Da documentação da AWS (12)
  • A backup plan defines when AWS Backup backs up assigned resources and how long it retains their backups.
  • A backup rule specifies a schedule, start and completion windows, target vault, lifecycle, and optional copy actions.
  • Backup plan resource assignments can select resource types or use tags and conditions; local assignments can target individual resource ARNs.
  • A backup vault is a container that stores and organizes backups, also called recovery points.
  • The vault KMS key encrypts backups with independent AWS Backup encryption; other backups inherit encryption from the source service.
  • For supported resource types, the first backup is full and later incremental backups contain changes; other resource types use full backups.
  • Continuous backups support point-in-time recovery, which restores to a chosen time; snapshot backups restore the captured state.
  • Continuous backup retention ranges from 1 to 35 days.
  • Backups transitioned to cold storage must remain there for at least 90 days, so deletion must be scheduled at least 90 days after transition.
  • When backup rule start windows overlap, AWS Backup optimizes backups using the rule with the longer retention period.
  • AWS Backup creates backups automatically through backup plans or manually as on-demand backups.
  • A backup rule can run snapshot backups every hour, 12 hours, day, week or month, or on a cron expression as often as hourly.

Cross-account copies

Cross-account copies place AWS Backup recovery pointsA saved backup that AWS Backup can use to restore a resource., or saved backups, in another account in the same organization. They can protect recovery data if the production account is compromised. For standard vaultsA container that stores and organizes recovery points., recovery follows a copy-then-restore sequence.

How it works

  1. The Organizations management account enables cross-account backup. Confirm that the resource type and Regions support copying.
  2. Create a non-default destination vault. Its resource policyA policy attached to a resource that specifies who may access it., which controls access to that vault, must allow the source caller to use backup:CopyIntoBackupVault.
  3. Give the source IAM roleAn AWS identity that a service assumes to perform permitted operations., an identity with backup permissions, backup:CopyFromBackupVault and backup:CopyIntoBackupVault in its identity policyA policy attached to a caller identity that grants its allowed actions..
  4. Permit destination-account access to the source customer managed encryption key, whose policy you control. For fully managed resources the destination can use aws/backup or a customer managed keyAn encryption key whose access policy the customer can manage.; other types require a customer managed key.
  5. Copy the backup, then restore in the destination account.

Exam cues

  • If the question says a vault policy allows copying but the operation is denied, think source role permissions and encryption-key access, because the vault policy is only one authorization requirement.
  • If the question says restore a standard-vault backup into another account, think copy first, because standard vaults do not provide a direct cross-account restore.
  • If the question says a destination account might leave the organization with backups, think a service control policyAn organization policy that limits permissions available to member accounts. (SCP) denying organizations:LeaveOrganization, because the account retains its copies after departure.

Remember

  • Same organization; cross-account backup enabled by the management account.
  • The default vault cannot be the destination.
  • Backups already in cold storage cannot be copied across accounts.

Trap: The standard-vault copy requirement does not describe every vault. AWS RAM sharing of a logically air-gapped vault permits a receiving account to restore without a preliminary copy.

Standard vault: copy before restoring
copy1restore2Source vaultAccount AiDestination vaultAccount BiRestore jobAccount Bi
  1. Copy a supported recovery point between standard vaults in accounts in the same organization.

  2. Start the restore from the destination account copy.

Detalhes das caixas (3)
Source vault

The source copy role needs permissions to copy out and into the destination vault.

Destination vault

Its vault policy allows the source caller to copy in. Configure the required key access.

Restore job

Restore the copied recovery point in the destination account with the required service-linked role.

Da documentação da AWS (14)
  • Standard cross-account backup copies require source and destination accounts in the same AWS Organizations organization.
  • Only the Organizations management account can enable or disable AWS Backup cross-account backup.
  • The source copy role needs backup:CopyFromBackupVault and backup:CopyIntoBackupVault in its identity policy.
  • The destination vault resource policy must allow backup:CopyIntoBackupVault for the source caller.
  • A customer managed key encrypting the source resource must allow the destination account to use it for a cross-account copy.
  • For fully managed resource types, the destination may use aws/backup or a customer managed key; other resource types require a customer managed key for cross-account copies.
  • AWS managed key policies cannot be modified to share access across accounts.
  • With standard vaults, copy the backup into the target account before restoring it there.
  • The destination for a standard cross-account copy cannot be the default vault.
  • AWS Backup does not support cross-account copies of backups in cold storage.
  • A destination account retains backups if it leaves the organization; an SCP denying organizations:LeaveOrganization can restrict this.
  • A logically air-gapped vault shared with AWS RAM permits restores in a receiving account without first copying the backup into that account.
  • Cross-account copy support depends on the resource type and AWS Regions involved.
  • A backup copy in another account can protect recovery data if the production account is compromised.

Cross-Region copies and PITR limits

Cross-Region copies keep AWS Backup recovery pointsA saved backup that AWS Backup can use to restore a resource., or saved backups, outside the source Region. A copy of a continuous backup is a snapshotA backup of resource data as captured at a particular time. of the resource, so it does not carry the source’s point-in-time recoveryRestoring data to a chosen time within a continuous backup retention period. (PITR) history.

How it works

  1. Check copy support for the resource type and both Regions. Choose a destination vaultA container that stores and organizes recovery points. and configure its encryption-key access.
  2. Add a copy action to the backup rule, or copy an eligible existing snapshot on demand. Continuous backups require a rule copy action; on-demand continuous copies are unsupported.
  3. For a continuous rule, AWS Backup takes and copies snapshots at the rule frequency. Destination copies restore to their captured state, without PITR.
  4. The first regional copy is full. Later copies are generally incremental when supported. For EBS, changing the destination vault key causes another full copy.

Exam cues

  • If the question says a copied continuous backup must support PITR in another Region, think snapshot limitation, because the copied recovery point has no PITR history.
  • If the question says Aurora needs backups in another Region, think supported AWS Backup snapshot copies, because native cross-Region automated snapshot-and-log replication is unsupported for Aurora clusters.
  • If the question says a remote Aurora recovery point must be fresh, account for copy time and queues, because a newer snapshot is not available until its copy completes.
  • If the question says an RDS copy fails because of persistent database options, think destination option group, because AWS Backup does not transfer a custom option group.

Remember

  • Copy support varies by resource and Region.
  • Backups already in cold storage cannot be copied across Regions.
  • Copies generally use the destination vault key. Copies of unencrypted Aurora, DocumentDB, and Neptune clusters remain unencrypted.

Trap: An Aurora AWS Backup copy and native RDS automated backup replication are different mechanisms. Aurora supports the snapshot-copy path; that copy does not gain PITR.

Continuous source, snapshot destination
rule copy1restore2Continuous backupSource RegioniSnapshot copyDestination RegioniRestore jobCaptured statei
  1. The continuous rule creates and copies a snapshot at its configured frequency.

  2. The destination restores the snapshot state, without point-in-time recovery.

Detalhes das caixas (3)
Continuous backup

The source provides point-in-time recovery within its retention period.

Snapshot copy

A supported rule copy action creates a periodic snapshot without PITR history.

Restore job

Restore the copied snapshot to the state captured when it was created.

Da documentação da AWS (13)
  • AWS Backup can copy supported backups to other Regions on demand or through backup plan copy actions.
  • Cross-Region and cross-account copy support depends on resource type and Region.
  • The first copy to a new Region is full; later copies are generally incremental if the service supports incremental backups.
  • For EBS, changing the destination vault encryption key causes a full copy; subsequent copies to the same vault and key remain incremental.
  • Cross-Region and cross-account copies of resources fully managed by AWS Backup use the destination vault key; a same-account cross-Region copy of a resource such as EBS into an aws/backup vault uses that service's AWS managed key; copies of unencrypted Aurora, DocumentDB and Neptune clusters stay unencrypted.
  • A continuous backup rule with a supported copy action produces periodic snapshot copies at the rule frequency.
  • Copies of continuous backups do not support point-in-time recovery in the destination.
  • AWS Backup does not support on-demand copies of continuous backups.
  • Backups in cold storage cannot be copied across Regions.
  • Aurora DB clusters do not support native cross-Region automated replication of snapshots and transaction logs.
  • AWS Backup supports cross-Region Aurora snapshot copies, including simultaneous cross-account and cross-Region copy.
  • Cross-Region Aurora snapshot copies can take hours and RDS can queue copy requests when many are in progress.
  • AWS Backup does not transfer a custom RDS option group during cross-Region copy; persistent options require a matching group to exist in the destination.

Vault Lock and air-gapped vaults

VaultA container that stores and organizes recovery points. Lock protects AWS Backup recovery pointsA saved backup that AWS Backup can use to restore a resource. against early deletion or lifecycleThe settings that determine when a backup changes storage tier and expires. changes. Its write-once, read-many model means backups remain readable while their retention periodThe length of time a backup is kept before it expires., the time they must be kept, is enforced.

How it works

  1. Select governance mode for a lock that authorized users can remove, or compliance mode for an immutable lock after grace timeThe period in which a compliance vault lock can still be changed or removed..
  2. For compliance mode, set ChangeableForDays to give at least 3 days to review the configuration. Omitting that parameter selects governance mode.
  3. For protected backups with direct sharing, use a logically air-gapped vault. It includes compliance-mode lock and stores backups in an AWS Backup service-owned account.
  4. Share that vault using AWS RAM, which grants other accounts access to the shared resource. Receiving accounts can restore directly, including accounts in another organization.
Protection Lock removal Recovery path
Standard vault, governance Authorized users can remove the lock Standard restore or copy workflow
Standard vault, compliance Immutable after grace time Standard restore or copy workflow
Logically air-gapped vault Compliance-mode lock built in Direct restore through RAM sharing

Exam cues

  • If the question says privileged users must not delete backups early, think compliance mode after grace time, because a governance lock can be removed.
  • If the question says another organization must restore directly, think a RAM-shared logically air-gapped vault, because it supports that sharing path.

Remember

  • Compliance grace time is at least 3 days.
  • A logically air-gapped vault defaults to an AWS owned key; a customer managed keyAn encryption key whose access policy the customer can manage. is optional.
  • A compliance-locked standard vault can be deleted when empty.

Trap: Governance mode does not prevent every privileged user from removing the lock. Compliance mode becomes immutable after its grace time.

Share protected backups for a direct restore
share1restore2Air-gapped vaultCompliance lockediResource shareAWS RAMiRestore jobReceiving accounti
  1. Share the logically air-gapped vault through AWS RAM.

  2. The receiving account restores from the shared recovery point.

Detalhes das caixas (3)
Air-gapped vault

Backups reside in a service-owned account and the vault has compliance-mode lock built in.

Resource share

Grant a receiving account access, including an account outside the organization.

Restore job

Restore from the shared vault without first copying into the receiving account.

Da documentação da AWS (10)
  • AWS Backup Vault Lock enforces write-once, read-many retention by rejecting early recovery point deletion and lifecycle changes.
  • A governance-mode vault lock can be removed by a user with sufficient IAM permissions.
  • After compliance grace time ends, no user or AWS can remove the lock; recovery points remain until their lifecycle completes.
  • Compliance-mode Vault Lock requires at least 3 days of grace time before the lock becomes immutable.
  • ChangeableForDays selects compliance mode; omitting it selects governance mode.
  • A compliance-locked vault can be deleted when it contains no recovery points.
  • A logically air-gapped vault has compliance-mode Vault Lock built in.
  • Logically air-gapped vaults use an AWS owned encryption key by default and optionally support a customer managed KMS key.
  • AWS RAM can share a logically air-gapped vault with other accounts, including accounts outside the organization, for direct restores.
  • Logically air-gapped vault backups are stored in an AWS Backup service-owned account.

Restore testing and audit evidence

AWS Backup restore testing runs scheduled restores and measures their duration. Add application validation to check that restored resources work, then use AWS Backup Audit Manager to compare resource restore time with a target.

How it works

  1. Create a restore testing plan with a schedule, start windowThe period in which a scheduled backup job is allowed to begin., source vaultsA container that stores and organizes recovery points., recovery pointA saved backup that AWS Backup can use to restore a resource. eligibility range, and latest or random selection.
  2. Assign protected resources and an IAM restore roleAn AWS identity that a service assumes to perform permitted operations., an identity with permission to restore them. Review the inferred restore parameters, such as subnet and encryption-key settings.
  3. AWS Backup runs the restore and records its duration. For validation, route an EventBridge COMPLETED restore event to a workflow such as a Lambda function that checks application health.
  4. Call PutRestoreValidationResult to record the validation outcome. A recorded validation status cannot be changed.
  5. AWS Backup deletes the test resources after validation completes or its window closes. If deletion fails, clean up manually and check the awsbackup-restore-test tagA key-value label used to select or describe a resource..
  6. Configure the Audit Manager restore-time control. It compares LatestRestoreExecutionTimeMinutes with maxRestoreTime in minutes.

Exam cues

  • If the question says provide recurring evidence of restore duration, think restore testing and the restore-time audit control, because they measure and evaluate resource restores.
  • If the question says confirm that an application works after restoration, think event-driven validation, because a completed restore job can trigger application checks.
  • If the question says a test cannot access a key or subnet, think restore parameters and role permissions, because restore testing needs those resources to complete.

Remember

  • Console validation retentionThe length of time a backup is kept before it expires.: 1 to 168 hours.
  • Restore-time control evaluation: every 24 hours.
  • AWS Backup provides no restore-time service-level agreementA contractual service guarantee, such as a commitment to a completion time. (SLA), a contractual time guarantee.

Trap: Resource restore duration and application validation are separate results. A duration below the audit target does not replace application health checks.

Restore, validate, and clean up test resources
complete1invoke2finish3Restore testAWS BackupiCompleted eventEventBridgeiValidationLambdaiCleanupAWS Backupi
  1. AWS Backup emits the restore completion event.

  2. EventBridge invokes the configured validation workflow.

  3. AWS Backup cleans up after validation or window expiry.

Detalhes das caixas (4)
Restore test

The scheduled test restores resources and records restore-job duration.

Completed event

A rule matches the restore job COMPLETED event.

Validation

Run application checks and report the result with PutRestoreValidationResult.

Cleanup

Delete test resources after validation completes or its window closes.

Da documentação da AWS (12)
  • AWS Backup restore testing schedules restore jobs and records their completion duration.
  • A restore testing plan sets the schedule, start window, source vaults, eligibility range, and latest-or-random recovery point selection.
  • Assign protected resources and an IAM restore role to the testing plan; AWS Backup infers restore metadata that can be overridden.
  • An EventBridge rule for a COMPLETED restore job can invoke a validation workflow such as a Lambda function.
  • PutRestoreValidationResult records the validation result for a restore job; a recorded validation status cannot be changed.
  • AWS Backup deletes test resources after optional validation completes or the validation window closes.
  • The console permits a validation retention window of 1 to 168 hours before test-resource cleanup.
  • A failed test-resource deletion requires manual cleanup; removing the awsbackup-restore-test tag can cause cleanup failure.
  • The Audit Manager restore-time control is noncompliant when LatestRestoreExecutionTimeMinutes exceeds maxRestoreTime, measured in minutes.
  • The Audit Manager restore-time control runs automatically every 24 hours.
  • AWS Backup provides no restore-time service-level agreement; times vary with system load and capacity.
  • Restore testing can fail because of missing subnet settings, an unassumable restore role, or insufficient resource and KMS-key permissions.

Organization backup policies

Organizations backup policies apply AWS Backup plans across accounts. Attach a policy to the organization root, an organizational unitA group of accounts within an AWS organization to which policies can apply. (OU, a group of accounts), or a single account to define its backup requirements centrally.

How it works

  1. The management account enables cross-account management. It can register a member account as a delegated administratorA registered member account with permission to perform administrative tasks across an organization., which gives that account backup administration duties.
  2. Provision the referenced vaultsA container that stores and organizes recovery points. in each target account and Region. Provision an IAM roleAn AWS identity that a service assumes to perform permitted operations., an identity AWS Backup can assume with permission to perform backups.
  3. Attach policies with backup rules, Regions, resource selections, and the role. Select resources by type or tagsA key-value label used to select or describe a resource..
  4. Inheritance combines applicable policies into the account’s effective policyThe policy produced by combining applicable inherited and directly attached policies.. Plans with the same name merge; differently named plans can coexist.
  5. Enable cross-account monitoring to inspect backup, copy, and restore activity centrally.

Exam cues

  • If the question says apply backup requirements to an OU, think an Organizations backup policy, because it creates plans in the affected accounts.
  • If the question says an inherited plan cannot run in a new account, think missing vaults or role permissions, because policy attachment requires those prerequisites.
  • If the question says target one resource by exact ARNAn identifier for an AWS resource that can be used in a resource assignment., think a local plan assignment, because organization policies select types or tags.

Remember

  • Management-account service opt-in settings govern Organizations-managed plans.
  • A delegated administrator is an account with backup administration duties.
  • Every referenced vault must exist in its target account and Region.

Trap: A centrally created plan does not provision its referenced vaults or IAM role. Create those before relying on the policy.

Apply backup policies across accounts
inherit1apply2Root policyOrganizationsiOU policyInherited settingsiAccount planAWS Backupi
  1. The OU inherits the root policy and combines it with applicable OU settings.

  2. The effective policy creates the corresponding account backup plan.

Detalhes das caixas (3)
Root policy

Attach common backup requirements at the organization root.

OU policy

Policies with matching plan names combine through inheritance.

Account plan

The effective policy creates a local plan; the vault and role must already exist.

Da documentação da AWS (9)
  • An Organizations backup policy creates corresponding backup plans in affected accounts.
  • Backup policies can attach to an organization root, organizational unit, or account and combine through policy inheritance.
  • The Organizations management account must enable AWS Backup cross-account management before policies manage multiple accounts.
  • Referenced backup vaults must exist in every target account and Region, and the referenced IAM role must exist and permit the backup.
  • Organizations backup policies select resource types or tags, not individual resource ARNs; use a local plan assignment for individual resources.
  • Policies with the same backup plan name merge into an effective backup policy for an account; policies with different plan names can coexist.
  • A registered AWS Backup delegated administrator is a member account that can manage backup policies and monitor jobs across accounts.
  • For Organizations-managed plans, management-account service opt-in settings override member-account settings, including delegated administrators.
  • Enabling cross-account monitoring lets the management account monitor backup, copy, and restore activity across the organization.

Backup operational checks

AWS Backup operations depend on resource selection, rule settings, permissions, and retentionThe length of time a backup is kept before it expires. bounds. Check each setting against the job or restore that failed.

How it works

  1. For a tag-only resource assignment, check service opt-in settings. They still apply to the selected resources.
  2. Review the backup rule’s console defaults for start time and windows. The completion windowThe time allowed for a backup job to finish after it starts. does not apply to Amazon FSx.
  3. For a database point-in-time recoveryRestoring data to a chosen time within a continuous backup retention period. (PITR) copy, check rds:DeleteDBSnapshot. AWS Backup uses it to remove a temporary source snapshotA backup of resource data as captured at a particular time.; without it, an expired recovery pointA saved backup that AWS Backup can use to restore a resource. can require manual deletion.
  4. Before restoring a copy in another account, ensure that account has the service-linked roleA role linked to an AWS service that permits that service to act in an account. for the resource’s service.
  5. Compare new backup and copy job retention with the vaultA container that stores and organizes recovery points.’s Vault Lock bounds. Incompatible jobs fail, while existing recovery points keep their lifecycles.

Exam cues

  • If the question says tagged resources are missing from a tag-only assignment, think service opt-in, because that setting still applies.
  • If the question says a database PITR copy leaves an expired source recovery point, think rds:DeleteDBSnapshot, because AWS Backup needs it to clean up the temporary snapshot.
  • If the question says a copy reached a new account but restore fails, think service-linked role, because the destination needs the role for the resource’s service.
  • If the question says jobs fail after Vault Lock retention bounds are set, think retention mismatch, because new jobs must meet those bounds.

Remember

  • Console start time: 00:30 in the local system time zone.
  • Console start windowThe period in which a scheduled backup job is allowed to begin.: 8 hours; completion window: 7 days. The completion window does not apply to Amazon FSx.

Trap: Vault Lock retention bounds do not rewrite existing recovery point lifecycles. They reject incompatible new backup and copy jobs.

Da documentação da AWS (7)
  • The destination account needs the service-linked role of the service whose resource it restores.
  • Database PITR copy jobs need rds:DeleteDBSnapshot to remove temporary source snapshots; missing permission can leave expired recovery points requiring manual deletion.
  • When resource assignment uses only tags, AWS Backup service opt-in settings still apply.
  • The backup rule console defaults to a start time of 00:30 in the local system time zone.
  • The backup rule console defaults to an 8-hour start window.
  • The backup rule console defaults to a 7-day completion window; the completion-window parameter does not apply to Amazon FSx.
  • Vault Lock retention bounds reject new backup and copy jobs with incompatible retention, but do not change existing recovery point lifecycles.

Flashcards

toque para virar
Resposta

·

Todos os 34 flashcards em lista

What does an AWS Backup plan define, and how are resources selected?

Rules define the schedule, windows, lifecycle, vault, and optional copies. Resource assignments select types, tags, or individual resource ARNs.

An AWS Backup design needs recovery to a chosen time within the retention period. Which backup type should it use?

Continuous backups for a supported resource type. Snapshot backups restore only their captured state.

Does every AWS Backup recovery point use the encryption key of its vault?

No. Independently encrypted backups use the vault key; other resource types inherit source-service encryption.

What minimum cold-storage residence and continuous-backup retention should an AWS Backup plan account for?

Cold storage requires at least 90 days after transition. Continuous backup retention is 1 to 35 days.

What is the most frequent snapshot schedule an AWS Backup plan rule supports?

Hourly, set as a frequency or with a cron expression. Use an on-demand backup for a one-off copy.

What prerequisites allow a standard AWS Backup cross-account copy?

Use accounts in the same organization, enable cross-account backup from the management account, allow the source role to copy out and in, and allow CopyIntoBackupVault in the destination vault policy. Use a non-default destination vault.

An encrypted AWS Backup cross-account copy fails even though its vault policy permits copying. What key settings should be checked?

Check source key sharing and the destination key type. AWS managed key policies cannot be shared; resource types not fully managed by AWS Backup require customer managed keys for cross-account copies.

Can AWS Backup restore from a standard vault in account A directly into account B?

No. Copy into account B first, then restore there. A shared logically air-gapped vault supports a different restore path.

Why keep AWS Backup copies in a separate account, and how can an organization restrict that account from leaving?

Cross-account copies can protect recovery data if the production account is compromised. An SCP denying organizations:LeaveOrganization restricts departure; an account that leaves retains its backups.

An AWS Backup cross-account copy has an Allow in the destination vault policy but still gets an authorization failure. Which identity permissions should be checked?

The source copy role needs backup:CopyFromBackupVault and backup:CopyIntoBackupVault. The destination Allow does not replace the source identity policy.

A team copies AWS Backup continuous backups to another Region and expects point-in-time recovery there. Is that supported?

No. Supported copy actions create periodic snapshots without destination PITR. Check the resource and Region support before configuring the copy.

An Aurora disaster recovery design proposes native RDS automated backup replication to another Region. What backup-copy approach fits Aurora?

Use supported AWS Backup Aurora snapshot copies. Aurora clusters do not support native cross-Region automated snapshot-and-log replication.

Why might an AWS Backup EBS copy become full after changing the destination encryption key?

Changing the destination vault key causes a full EBS copy. Repeated copies to the same vault and key can remain incremental.

Can AWS Backup create an on-demand cross-Region copy of a continuous backup?

No. Use a supported copy action in a continuous backup rule to create periodic snapshot copies.

An Aurora recovery plan needs a fresh snapshot in another Region. Why must it account for copy delays?

Cross-Region copies can take hours and may queue, delaying the availability of the newer recovery point.

How do governance and compliance modes differ in AWS Backup Vault Lock?

Governance locks can be removed by authorized users. Compliance locks become immutable after grace time of at least 3 days; backups remain protected until their lifecycle completes.

What protects an AWS Backup logically air-gapped vault, and how can another account restore from it?

Built-in compliance-mode Vault Lock and encryption with an AWS owned key by default. AWS RAM sharing allows another account to restore directly; a customer managed key is optional.

An AWS Backup design must reject early backup deletion even by privileged users. Which Vault Lock mode should it use?

Compliance mode after its grace time expires. Governance mode remains removable by users with sufficient IAM permissions.

A team needs to restore AWS Backup data from an account outside its organization without first copying recovery points. Which vault can provide this?

A logically air-gapped vault shared through AWS RAM. Its sharing supports receiving accounts outside the organization.

What does an AWS Backup restore testing plan configure and measure?

It schedules restores from selected vaults using eligible latest or random recovery points, assigned resources, and a restore role. It records restore-job duration and cleans up test resources.

Does a completed AWS Backup restore test automatically establish that the restored application works?

Add application validation. A COMPLETED restore event can trigger a Lambda workflow through EventBridge, and PutRestoreValidationResult records its outcome.

Auditors need scheduled AWS Backup evidence that resource restores meet a target duration. What should the team configure?

Restore testing plus the AWS Backup Audit Manager restore-time control. Set maxRestoreTime in minutes and compare it with recorded restore execution time.

An AWS Backup test resource must remain available while automated health checks run. Which setting controls cleanup timing?

Set the validation retention window, from 1 to 168 hours in the console. Cleanup follows completed validation or window expiry.

An AWS Backup restore-time audit control passes. Does AWS guarantee future restores meet that duration?

No. AWS Backup has no restore-time SLA. The control evaluates recorded execution time against the configured target.

An AWS Backup restore testing job reports failed resource deletion. What must the operator do?

Clean up the restored resource manually. Check whether the awsbackup-restore-test tag was removed.

How can an organization apply AWS Backup plans to multiple accounts?

Enable cross-account management, then attach an Organizations backup policy to the root, an OU, or accounts. Provision the referenced vaults and IAM role in the target accounts and Regions.

An Organizations AWS Backup policy references a vault and IAM role that are absent in a member account. Does attaching the policy create those prerequisites?

No. Provision the vault and role before the plan runs. The policy creates the plan, not these prerequisites.

A team needs an Organizations AWS Backup policy to protect one resource by its exact ARN. Which assignment should it use?

Use a local backup plan assignment. Organization policies select resource types or tags, not individual resource ARNs.

Which service opt-in settings control an AWS Backup plan managed through Organizations?

The management account settings override member-account settings for that plan, even when a delegated administrator manages it.

An AWS Backup copy reached a new account, but restoring a resource from a service never used there fails. What prerequisite may be absent?

The destination service-linked role. Ensure that the underlying service has created its role in that account.

An AWS Backup database PITR copy leaves an expired source recovery point. Which cleanup permission should be checked?

rds:DeleteDBSnapshot. AWS Backup needs it to delete the temporary source snapshot after the copy.

An AWS Backup plan selects resources only by tags, but tagged resources are not protected. Which setting should the team inspect?

Check service opt-in settings, because tag-only selections still respect them.

What are the AWS Backup console defaults for a rule start time and its start and completion windows?

00:30 in the local system time zone, an 8-hour start window, and a 7-day completion window. The completion window does not apply to FSx.

Do new AWS Backup Vault Lock retention bounds rewrite the retention of existing recovery points?

No. Existing recovery points keep their lifecycle. Incompatible new backup or copy jobs fail.

Você concluiu todos os tópicos da DOP-C02!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified DevOps Engineer - Professional (DOP-C02) no Easy Review. Venha estudar também!