To ensure the most accurate results when inputting the data into the VMware Cloud on AWS Sizer, using the Advanced Sizer in 'import' mode and importing the Live Optics data is the best method. This approach automatically sets the values for vCPU, vRAM, utilized storage, IOPS, and I/O based on the detailed analysis captured by Live Optics, ensuring that the specific characteristics of the Microsoft SQL and Oracle workloads are accurately reflected without relying on manual input or default values.
To create a single broadcast domain for virtual machines both in the data center and in the software-defined data center (SDDC) over a DirectConnect connection without adding additional components in the cloud, the administrator can deploy a Layer 2 Virtual Private Network (L2VPN). This will allow for seamless network extension, keeping the virtual machines within the same subnet and broadcast domain across both environments.
Reducing the risk of migrating applications to the cloud by removing the need for application transformation is one of the benefits, as it allows a lift-and-shift approach where applications can be moved without modification. Maintaining existing investment in skills and toolsets is another benefit because the skills required to manage the on-premises SDDC environment are applicable to VMware Cloud on AWS, allowing for a smoother transition with less need for retraining.
To scale out the VDI solution quickly, the administrator should: Deploy a new VMware Horizon pod on VMware Cloud on AWS (to utilize cloud resources and quickly scale), configure network connectivity and firewall rules to allow communications between on-premises and VMware Cloud on AWS connection servers (to ensure seamless integration), and connect the two VMware Horizon pods together using a Horizon Cloud Pod Architecture (CPA) (to manage them together and provide a unified environment).
When planning to relocate workloads into VMware Cloud on AWS, especially for a system involving a variety of workloads for a corporate customer relationship management (CRM) system, it's essential to consider profiles that will cater to such workloads. Databases such as Oracle and Microsoft SQL Server are commonly used in CRM systems, so profiles for these are necessary. Additionally, general purpose application VMs are critical as the CRM system likely involves various application workloads. Therefore, the three profiles that the administrator could create in the VMware Cloud on AWS Sizer are Databases - Oracle, Databases - Microsoft SQL Server, and General Purpose (Application VMs). The other options, like VDI clones, are less relevant to a CRM system.