1Z0-1072-25 exam dumps: questions 201 to 300 of 318

Correct answers: B, C

• A. Incorrect.

  Incorrect. Detaching a boot volume from a running production instance requires stopping that instance, causing downtime. This conflicts with the requirement to minimize disruption during business hours.

• B. Correct.

  Correct. Creating a boot volume backup does not require stopping the instance, and you can directly use this backup to launch a new compute instance in the desired compartment.

• C. Correct.

  Correct. Creating a custom image from the production instance� boot volume captures the OS configuration without taking the production instance offline. You can then create a new instance using that custom image in another compartment.

• D. Incorrect.

  Incorrect. Resizing the production boot volume might be done online, but attaching the same volume to a different instance in read-only mode does not allow the new instance to boot from it. Boot volumes must be attached in 'boot' mode, which would conflict with the need to keep the production system running.

• E. Incorrect.

  Incorrect. While exporting and importing images via Object Storage is possible for some custom image workflows, it is not the most direct or recommended approach for quickly replicating a boot volume within the same region. Boot volume backups or custom images provide simpler, faster paths.

Correct answer: A

• A. Correct.

  Correct. OCI allows you to resize block volumes without detaching them, minimizing downtime. After the volume is expanded, you must resize the partition and filesystem in the operating system to make the additional capacity available.

• B. Incorrect.

  Incorrect. While you can detach and then resize the volume, this approach requires instance downtime for detachment, and the filesystem does not automatically expand. You still need to expand the filesystem at the OS level.

• C. Incorrect.

  Incorrect. Copying data to a new volume is more time-consuming and disrupts availability during the copy or reattachment, leading to more downtime than necessary.

• D. Incorrect.

  Incorrect. Shutting down the instance causes more downtime, which is not minimal. OCI supports online resizing of block volumes without shutting down the compute instance.

Correct answer: B

• A. Incorrect.

  Option 1: This approach would work technically, but it is not the most efficient or minimally disruptive. Detaching the volume and manually copying data would cause significant downtime for a mission-critical application.

• B. Correct.

  Option 2: This is correct. Oracle Cloud Infrastructure allows you to resize a block volume in-place through the Console or CLI while it remains attached to the instance. After resizing the volume, you must extend the file system within the operating system to utilize the new space. This method minimizes downtime because the application can continue running during most of the process.

• C. Incorrect.

  Option 3: Stopping the entire compute instance is unnecessary for resizing a block volume. While you could create a larger volume and migrate, it is more disruptive than resizing in-place and is not ideal when minimal downtime is required.

• D. Incorrect.

  Option 4: Creating a full backup and then restoring it as a larger boot volume is a more complex operation and does not directly apply to resizing a data-only block volume. Boot volumes store the operating system, while the data resides on a separate block volume in this scenario.

Correct answers: C, D

• A. Incorrect.

  Option 1: Although creating a volume backup and restoring it in AD2 can work for just the data volume, it does not address the boot volume or the minimal downtime requirement if you also need an exact copy of the OS environment. Also, you would need to handle the boot volume separately to fully replicate the environment.

• B. Incorrect.

  Option 2: Stopping the Compute instance to perform offline resizing causes downtime, which contradicts the requirement to minimize downtime. While offline resizing is a valid approach in some scenarios, Oracle Cloud Infrastructure supports online resizing for block volumes, making this option unnecessary for minimal downtime scenarios.

• C. Correct.

  Option 3 (Correct): Using the online volume resizing feature allows you to expand your block volume from 500 GB to 1 TB without detaching it from the running instance. This meets the requirement for minimal downtime.

• D. Correct.

  Option 4 (Correct): Creating a volume group backup that includes both boot and block volumes allows you to restore the entire environment in AD2 in one operation. This approach ensures that your OS and data are in sync and simplifies migration compared to individually backing up boot and block volumes.

• E. Incorrect.

  Option 5: Cross-region replication is designed for automatically replicating block volumes across different regions, not between availability domains within the same region. Therefore, this does not meet the requirement to migrate from AD1 to AD2 in the Ashburn region.

Correct answers: A, C

• A. Correct.

  Option 1 is correct. By grouping both block volumes into a single volume group, you can perform a single backup operation that captures a crash-consistent view of all volumes. This simplifies management and ensures the database files stored across multiple volumes are consistently backed up at once.

• B. Incorrect.

  Option 2 is incorrect. Replicating block volumes to Object Storage before backing them up individually does not guarantee a single crash-consistent backup across volumes. It also adds complexity and is not the recommended approach for ensuring quick recovery or simplified test environment creation.

• C. Correct.

  Option 3 is correct. OCI allows you to create clones of volume groups quickly. This is especially useful when you need to spin up a test environment on short notice, as it provides a near-instant copy of the entire data set without disrupting the production environment.

• D. Incorrect.

  Option 4 is incorrect. Scheduling separate backups for each volume can lead to inconsistencies if writes occur during backup creation on different volumes at different times. A volume group backup is the recommended way to ensure crash consistency across multiple volumes used by the same database.