1Z0-1072-25 Question 249
Single answerYou have an existing version-enabled standard-tier bucket in the Phoenix region and want to set up cross-region replication to an archive-tier bucket in the Ashburn region. However, when creating the replication policy on the source bucket, you encounter an error indicating incompatible bucket configurations. Which action should you take to properly configure replication?
- A
Enable versioning on the archive-tier bucket in the Ashburn region
- B
Disable versioning on the Phoenix bucket to match the archive-tier bucket
- C
Enable client-side encryption on both buckets before retrying the replication policy
- D
Remove the archive tier on the Ashburn bucket and switch it to standard tier
Show answer and explanation
Correct answer: A
Explanation
In Oracle Cloud Infrastructure, cross-region replication requires that critical configurations match between source and target buckets. If your source bucket is version-enabled, the target must also be version-enabled�even if it uses a different storage tier (standard or archive). For more details, refer to Oracle's official documentation on configuring cross-region replication.
- A. Correct.
Correct. When the source bucket is version-enabled, the target bucket must also have versioning enabled for cross-region replication to succeed, even if you are replicating from a standard-tier bucket to an archive-tier bucket.
- B. Incorrect.
Incorrect. While disabling versioning on the source could allow replication to proceed, it is typically undesirable because it removes the benefits of version control and object history on the source. The recommended practice is to match the versioning settings on both buckets.
- C. Incorrect.
Incorrect. Cross-region replication in OCI relates to bucket-level settings (like versioning), not mandatory client-side encryption. Having encryption enabled on one or both buckets is a separate consideration and is not the root cause of the mismatch error here.
- D. Incorrect.
Incorrect. You can replicate from a standard-tier bucket to an archive-tier bucket if the configurations are aligned (e.g., versioning settings). Changing the Ashburn bucket to standard tier rather than enabling versioning is unnecessary and does not address the core mismatch.