5V0-21.21 Exam questions (80-89) vSAN考试题目

5V0-21.21 Exam questions

To study for VMware HCI Master Specialist Exam | vSAN认证考试题目学习

82. An administrator has decided to switch the Preferred Fault Domain in a vSAN stretched cluster. Resynchronization activity increased drastically after this change.
Which action should the administrator take next time to avoid this problem?

  • A. Changing the Data Locality setting to None.
  • B. Adding additional hosts to both domains in existing vSAN cluster.
  • C. Adding disks to hosts and creating additional disk groups.
  • D. Putting all hosts from Secondary domain into maintenance mode.

Explaination:

Based on the information from VMware’s documentation, when an administrator switches the Preferred Fault Domain in a vSAN stretched cluster, it can indeed lead to an increase in resynchronization activity. This happens because objects with the ‘Data locality=Preferred’ policy setting always move to the Preferred fault domain, and objects with the ‘Data locality=Secondary’ setting move to the Secondary fault domain. When the domains are swapped, these objects move from one site to the other, triggering increased resynchronization.

To avoid this unnecessary resynchronization, the recommended action is to change the Data locality setting to None before swapping the Preferred and Secondary domains. Once the domains have been swapped back, the Data locality setting can be reset. This approach helps to mitigate the increase in resynchronization activity that occurs due to the domain switch​.

This is more effective than the other options for this specific scenario, as it directly addresses the root cause of the increased resynchronization activity. Adding additional hosts or disks might improve overall cluster performance and capacity but does not directly relate to the issue of resynchronization caused by changing the Preferred Fault Domain. Similarly, putting hosts in maintenance mode is not a solution to this problem and could disrupt normal operations.

82. 一位管理员决定在vSAN拉伸集群中切换首选故障域。在这次变更之后,重新同步活动急剧增加。下一次,管理员应该采取哪种措施来避免这个问题?

  • A. 将数据本地化设置更改为无。
  • B. 在现有vSAN集群的两个域中添加额外的主机。
  • C. 向主机添加磁盘并创建额外的磁盘组。
  • D. 将次要域的所有主机置于维护模式。

解释:

根据VMware的文档信息,当管理员在vSAN拉伸集群中切换首选故障域时,的确可能导致重新同步活动增加。这是因为设置了“数据本地性=首选”的对象总是移动到首选故障域,而设置了“数据本地性=次要”的对象移动到次要故障域。当域被交换时,这些对象从一个站点移动到另一个站点,触发了重新同步的增加。

为了避免这种不必要的重新同步,建议在交换首选和次要域之前将数据本地性设置更改为无。一旦域被换回,可以重置数据本地性设置。这种方法有助于减轻由于域切换导致的重新同步活动增加。

图书推介 - 京东自营

24小时热门

还有更多VMware问题?

免费试下我们的VMware问答小助理,即时解答VM难题 → 🤖VM技术助理

需要协助?或者只是想技术交流一下,直接联系我们!

推荐更多

虚拟机CPU重配置失败 - 参数不正确: configspec.numcorespersocket
疑难杂症

虚拟机CPU重配置失败 – 参数不正确: configspec.numcorespersocket

在 vSphere 7.x 和 8.x 中,调整虚拟机 CPU 数量时,可能会遇到 A specified parameter was not correct configspec.numcorespersocket 错误。原因是 CPU 核心数需为原配置的整数因子。解决方案包括使用 “Assign at power on” 选项,允许系统在启动时自动分配核心数,从而避免该错误。

如何在博通网站查询VMware ESXi的兼容性
VMware快速入门

如何在博通网站查询VMware ESXi的兼容性

本文介绍了如何在博通网站查询VMware ESXi的兼容性,尤其是针对服务器BIOS固件和I/O设备的驱动与固件要求。通过详细的步骤,读者可以轻松查找特定硬件与ESXi版本的兼容性信息,确保虚拟化环境的稳定运行。文章以Dell PowerEdge R7525服务器和PERC H755阵列卡为例,提供了清晰的操作指南。

ESXi 7.0不再支持的硬件设备(ESXi 7.0后已移除支持的设备列表)
运维必备

ESXi 7.0不再支持的硬件设备(ESXi 7.0后已移除支持的设备列表)

本文介绍了 ESXi 7.0 中不再受支持的设备和已移除支持的设备的分类,重点讲解了这些设备对升级过程的影响及潜在风险。文章还提供了升级时应注意的设备兼容性问题,帮助系统管理员避免存储、网络和配置丢失等不可恢复的后果。

ESXi 9.0只支持UEFI启动,不再支持传统BIOS?
VM新闻

ESXi 9.0只支持UEFI启动,不再支持传统BIOS?

ESXi 9.0 可能彻底取消对传统 BIOS 的支持,仅允许 UEFI 启动。虽然 VMware 尚未明确宣布,但官方文档和行业趋势表明 Legacy BIOS 正在被逐步淘汰。企业应尽早评估服务器固件状态,并做好向 UEFI 迁移的准备,以确保兼容性和稳定性。