An administrator is attempting to configure Storage I/O Control (SIOC) on five datastores within a vSphere environment. The administrator is being asked to determine why SIOC configuration completed successfully on only four of the datastores.
What are two possible reasons why the configuration was not successful? (Choose two.)
Storage I/O Control (SIOC) cannot be configured on datastores that contain Raw Device Mappings (RDMs) or that have multiple extents. These limitations prevent SIOC from being successfully configured on certain datastores despite the support for various other storage types such as Fibre Channel, iSCSI, and NFS.
Storage I/O Control is supported on Fibre Channel-connected, iSCSI-connected, and NFS-connected storage. Raw Device Mapping (RDM) is not supported. Storage I/O Control does not support datastores with multiple extents.
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-37CC0E44-7BC7-479C-81DC-FFFC21C1C4E3.html#:~:text=El%20control%20de%20E/S%20de%20almacenamiento%20se,no%20admite%20almacenes%20de%20datos%20con%20m%C3%BAltiples%20extensiones.
Answer: AC
Storage I/O Control (SIOC) on datastores has the following limitations: - Datastores that are SIOC-enabled must be managed by a single vCenter Server system. - SIOC is supported on Fibre Channel-connected, iSCSI-connected, and NFS-connected storage. Raw Device Mappings (RDMs) are not currently supported. - Datastores with multiple extents are not supported by SIOC. - Before using SIOC on datastores that are backed by arrays with automated storage tiering capabilities, you should check the VMware Storage/SAN Compatibility Guide to verify whether your automated tiered storage array has been certified to be compatible with SIOC.
Two possible reasons why Storage I/O Control (SIOC) configuration might not be successful on a datastore are: A. The datastore contains Raw Device Mappings (RDMs): SIOC does not work with datastores containing Raw Device Mappings. C. The datastore has multiple extents: SIOC is not supported on datastores with multiple extents. SIOC is generally compatible with different storage types, including ISCSI and NFS, as long as they meet the other requirements and constraints of SIOC. The type of disks (e.g., SAS) typically doesn't affect SIOC configuration.
A&C https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-37CC0E44-7BC7-479C-81DC-FFFC21C1C4E3.html - Storage I/O Control is supported on Fibre Channel-connected, iSCSI-connected, and NFS-connected storage. Raw Device Mapping (RDM) is not supported. - Storage I/O Control does not support datastores with multiple extents.
yes finally
To ensure compliance with the company policy for time synchronization, the administrator should take the following step: C. Ensure that each ESXi host is configured to use a Network Time Protocol (NTP) source. The company policy states that all physical servers must synchronize time with an external time source that is accurate to the microsecond. In VMware environments, ESXi hosts are responsible for timekeeping within the virtual infrastructure. By configuring each ESXi host to use a Network Time Protocol (NTP) source, the administrator can ensure that the hosts synchronize their time with a reliable external time source. NTP is a widely used protocol for time synchronization and provides sufficient accuracy for most enterprise environments.
The correct answers are A and E. Storage I/O Control (SIOC) is a feature of VMware vSphere that helps to improve storage performance by managing the I/O workload across all virtual machines on a datastore. SIOC can only be configured on datastores that meet the following requirements:
AC is correct, NFS 3 support storage IO control & in option E no NFS version mentioned.
AC is correct