A DNS A record is necessary to resolve the hostname (lcm.vcf.company.com) to the specified IP address (10.0.0.150) so that it can be correctly accessed during the deployment.
A DNS PTR record is required for reverse DNS lookup, which ensures proper identification of the IP address (10.0.0.1) to the hostname (lcm.vcf.company.com), which is important for network validation during the deployment process.

Password rotation for VMware Cloud Foundation components is managed via the SDDC Manager UI. In the password management section of the SDDC Manager, administrators can rotate the passwords for various components like vCenter Server, NSX Manager, and other management components.

In a VMware Cloud Foundation environment, it is recommended to use static IP addresses that are managed via VMware NSX IP Pools. This method ensures consistency, scalability, and centralized management of IP addresses, which is essential for large environments. NSX IP Pools allow for efficient IP address allocation and management.

Within a vSphere Namespace, administrators have the ability to configure resource limits to control the amount of resources that workloads can consume. According to the official VMware Cloud Foundation documentation, the three types of resource limits that can be set on a vSphere Namespace are:
CPU:The administrator can specify the maximum CPU resources that can be used within the namespace.
Memory:The administrator can define the maximum amount of memory allocated to workloads in the namespace.
Storage:The administrator can configure storage limits, specifying how much storage capacity is available to the namespace.
These resource limits are essential for managing and isolating resources across different namespaces to prevent resource contention and ensure fair resource distribution. The documentation clearly states that there is no option to set a resource limit based on the number of containers or network bandwidth within the vSphere Namespace configuration. The focus is solely on controlling CPU, memory, and storage resources.

Memory Hot Add must be enabled before you can add RAM to a running VM.
CPU Hot Add must be enabled before adding vCPUs to a powered-on VM.
You can only toggle the Hot Add features (CPU or Memory) when the VM is powered off.