When planning a lift-and-shift migration of virtual machines from an on-premises VMware environment to OCI Compute, which THREE key readiness assessments must be performed prior to migration? (Choose three.)
Trap 1: Convert all block storage volumes directly into OCI Autonomous…
Block volumes contain file systems and OS partitions, which cannot be directly converted into a managed relational database service.
- A
Analyze CPU and memory utilization metrics to select appropriate OCI Compute shapes.
Right-sizing instances based on actual workload metrics prevents over-provisioning or performance bottlenecks in OCI.
- B
Upgrade the on-premises VMware hypervisor version to the exact software stack used by Oracle Cloud VMware Solution (OCVS).
This is unnecessary unless specifically migrating to OCVS; standard lift-and-shift to OCI Compute does not require VMware hypervisor matching.
- C
Convert all block storage volumes directly into OCI Autonomous Database instances.
Why wrong: Block volumes contain file systems and OS partitions, which cannot be directly converted into a managed relational database service.
- D
Map source network topologies, IP addressing, and security lists/NSGs to OCI Virtual Cloud Networks (VCNs) and subnets.
Network planning is critical to ensure proper connectivity and security posture post-migration.
- E
Verify guest operating system compatibility with OCI supported images and kernel versions.
Ensuring the OS is supported by OCI ensures successful booting and driver availability.