5V0-21.21 Exam questions (70-79) vSAN考试题目

5V0-21.21 Exam questions

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

78. A company has deployed a 12-node (6-6-1) vSAN 7.0 stretched cluster for all production workloads.

The customer currently uses two different vSAN storage policies for running the workloads depending on the applications requirements:

  • Policy 1-Site Disaster Tolerance=Dual Site Mirroring, FTT=Erasure Coding
  • Policy 2-Site Disaster Tolerance=Dual Site Mirroring, FTT=Mirroring

During the setup of the vSAN stretched cluster, the following VM/Host Rules were created:

  • Preferred Site – Preferred Site workloads should run on DC1 hosts.
  • Secondary Site – Secondary Site workloads should run on DC2 hosts.

Which two actions should the administrator take to ensure that there is no impact to production services before completing the maintenance window in the Preferred Site?(Choose two.)

  • A. Update the Preferred Site vSphere DRS affinity rule to be “Should not run on hosts in group”.
  • B. Change the Host Groups in the Preferred Site rule to the DC2 hosts.
  • C. Update the Preferred Site v Sphere DRS affinity rule to be ‘Must run on hosts in group’.
  • D. Change the Host Groups in the Secondary Site rule to the DC1 hosts.
  • E. Update the Secondary Site vSphere DRS affinity rule to be ‘Must run on hosts in group’.

Explaination:

Based on the scenario described for maintaining production services during maintenance in a vSAN stretched cluster, the two actions that the administrator should take are:

A. Update the Preferred Site vSphere DRS affinity rule to be “Should not run on hosts in group”: This is a partially correct approach but requires a slight modification. Ideally, the rule should be updated to “Should run on hosts in group” for the DC2 hosts. This modification ensures that the workloads, which are normally preferred to run on DC1 hosts, are preferentially moved to DC2 during the maintenance of the Preferred Site, thereby minimizing impact.

E. Update the Secondary Site vSphere DRS affinity rule to be ‘Must run on hosts in group’: This action enforces that the Secondary Site workloads strictly adhere to running on the DC2 hosts. This is important during the maintenance of the Preferred Site (DC1) to prevent any accidental migration or loading of additional workloads onto the DC1 hosts, which could impact performance or availability.

Choosing these two actions helps in balancing the load and ensuring continuous operation of services during the maintenance window. It’s crucial to manage workload distribution effectively between the preferred and secondary sites in a stretched cluster environment to maintain service continuity.

78. 一家公司已经部署了一个12节点(6-6-1)的vSAN 7.0伸展集群,用于所有生产工作负载。

客户目前根据应用程序的要求,使用两种不同的vSAN存储策略来运行工作负载:

  • 策略1-站点灾难容忍=双站点镜像,FTT=纠删码
  • 策略2-站点灾难容忍=双站点镜像,FTT=镜像

在设置vSAN伸展集群时,创建了以下虚拟机/主机规则:

  • 首选站点 – 首选站点工作负载应在DC1主机上运行。
  • 次要站点 – 次要站点工作负载应在DC2主机上运行。

在首选站点维护窗口完成之前,管理员应采取哪两项措施以确保对生产服务没有影响?(选择两项。)

  • A. 更新首选站点vSphere DRS亲和性规则为“不应在组内主机上运行”。
  • B. 将首选站点规则中的主机组更改为DC2主机。
  • C. 更新首选站点vSphere DRS亲和性规则为“必须在组内主机上运行”。
  • D. 将次要站点规则中的主机组更改为DC1主机。
  • E. 更新次要站点vSphere DRS亲和性规则为“必须在组内主机上运行”。

解释:

根据维护vSAN伸展集群期间维持生产服务的场景描述,管理员应采取的两项行动是:

A. 更新首选站点vSphere DRS亲和性规则为“不应在组内主机上运行”:这是一个部分正确的方法,但需要稍作修改。理想情况下,规则应更新为“应在DC2主机组内运行”。此修改确保在首选站点(DC1)维护期间,通常倾向于在DC1主机上运行的工作负载被优先移动到DC2,从而最小化影响。

E. 更新次要站点vSphere DRS亲和性规则为“必须在组内主机上运行”:此举措强制次要站点工作负载严格遵循在DC2主机上运行。在首选站点(DC1)维护期间,这一点很重要,以防止任何意外迁移或在DC1主机上加载额外工作负载,这可能影响性能或可用性。

选择这两项行动有助于在维护窗口期间平衡负载并确保服务的连续运行。在伸展集群环境中有效管理首选和次要站点之间的工作负载分配对于维持服务连续性至关重要。

图书推介 - 京东自营

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 迁移的准备,以确保兼容性和稳定性。