Exam 3V0-21.21 All QuestionsBrowse all questions from this exam
Go to Exam
Question 37

An architect is tasked with designing a greenfield VMware software-defined data center (SDDC) solution that will be used to deliver a private cloud service for a customer.

During the initial meeting with the service owner and business sponsor, the customer has provided the following information to help inform the design:

✑ The solution must support the concurrent running of 1,000 virtual machines

✑ The production environment must be delivered across two geographically dispersed data centers

✑ All virtual machines must be capable of running in either data center.

✑ The two data centers are currently connected to each other through a single but diversely routed, high bandwidth and low latency link.

✑ The link between the two data centers is capable of supporting a round-trip time (RTT) of 150 ms

✑ The existing server hardware standard document states that all virtual infrastructure hosts must be deployed using vSAN ReadyNodes

✑ The service owner has stated that it is critical to ensure the availability target of 99.9%

✑ All virtual machine backups must be completed using the existing backup service

✑ The recovery time objective (RTO) for the service is five minutes

✑ The recovery point objective (RPO) of the service is four hours

Which two elements represent risks to the successful delivery of this solution? (Choose two.)

    Correct Answer: B, E

    The network connectivity between the data center sites poses a risk because it is connected through a single link, even if diversely routed, creating a potential single point of failure. The existing backup service is also a risk because it may not be capable of meeting the stringent RTO and RPO requirements, which are critical for ensuring service availability and recovery objectives.

Discussion
estornudoOptions: BE

I'd say risks are B and E B because it has a single link between sites E because existing backup service may not be OK wit such as low RPO and RTO requirements

Alchot

Then E is an assumption to be OK or not OK and can turn into a risk at the same time. E because existing backup service may not be OK wit such as low RPO and RTO requirements Without making assumptions BD are more accurate. Single link. Risk of SPOF Latency can break some applications to run from either site and even the cluster performance.

amgiceOptions: AD

A - for strech cluster need a witness site too D - RTT needs to be less than 5ms betwen sites

mvojka1990

VM running in either DC, not across DCs, so no need for stretched cluster, ok its SDDC but not stretched SDDC clusters mentioned, and also no need for a Witness 3rd site. RTT 150 is OK, because its capable to run long-distance vmotion, so, one risk is having existing backup service because you have aggressive RPO RTO with a lot of VMs and you will be not sure if its capable to run the new SDDC platform, and also if that single link goes down you lose site connection . Final answer B,E.

diegof1Options: BD

B & D B: Because the two data centers are currently connected to each other through a single but diversely routed D: Because the RTT on the link between the two data centers is 150 ms and the requirement for vSAN stretched cluster is 5ms between sites. Using vSAN stretched cluster should be the best design for all requirements

primanturinOptions: BE

B and E I do not really see in the question any mention about vSAN stretched cluster. Anyway, I believe it can be discarded because of the RTO and RPO requirements. A vSAN stretched cluster achieves an RPO of 0 and a very low RTO https://blogs.vmware.com/virtualblocks/2017/02/09/vsan-srm-rpo-rto/ B - Single link between sites - Risk E - The existing backup service might not be able to accomplish such a low RTO and RPO requirements - Risk Obviously, if they were talking about a vSAN stretched cluster, the answer would have been A and D.

TabordensOptions: BE

B and E

PSE_ITOptions: BE

totally agree with estornudo B because it has a single link between sites E because existing backup service may not be OK wit such as low RPO and RTO requirements

lifeflakesOptions: BE

considering that this is not a Zero RPO, but 4 hours of RPO, is clearly not a vSAN stretched cluster requirement. Also with vSphere 6.0 Long-distance vMotion, the round-trip latency limit for vMotion networks is up to 150 milliseconds. I would go with B & E.

cyberwookieOptions: AB

Single Link = Risk Existing Backup: Is RTO/RPO still achievable? Dunno, Risk

FR_WolfmanOptions: BE

Answer is B & E A >> The SLA can be achieve with only 2 datacenters. There is no risk B >> We have a SPOF here due to the single link. It is a risk. C >> The use of vSAN ReadyNodes is a constraint, not a risk D >> The RTT is not a risk. It may be constraint, as a 150ms RTT latency will exclude the option to deploy a vSAN Stretched Clusters E >> The existing backup service may not be able to reach the required RTO/RPO. It is a risk

83f7706Options: BD

B+D 150 RTT it is risk for 1000 (10+ESXi hosts) https://docs.vmware.com/en/VMware-vSphere/7.0/vsan-network-design-guide/GUID-F3401655-6EFA-477B-B072-E8F001B50BCC.html

LFC1280Options: BD

I'd go with B and D. B: Single link is a clear risk of SPOF. D: The latency may not allow to comply with the RPO and RTO requirements. It is stated that the Intersite Link has high bandwidth and low latency link, but then it says that is capable of supporting RTT of 150 ms. Despite being intentionally confusing, there is a latency number (exact one) which could not satisfy a RPO of 5 minutes for a 1000 VMs. That is the risk. The fact that we are forced to use the existing backup solution is not a risk per se, but a constraint. Sounds good?

andr3Options: BD

The network connectivity between data center sites & The RTT on the link between the two data centers

diegof1Options: BD

B & D B: Because the two data centers are currently connected to each other through a single but diversely routed D: Because the RTT on the link between the two data centers is 150 ms and the requirement for vSAN stretched cluster is 5ms between sites. Using vSAN stretched cluster should be the best design for all requirements https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-AFF133BC-F4B6-4753-815F-20D3D752D898.html

MezzeOptions: AD

I think that A & D correct.

cib28Options: BE

B and E not D because RTT is 150 ms; it'ok ok for Long Distance vMotion https://kb.vmware.com/s/article/2106949

zhongzhong5011Options: AD

REQ: VSAN RPO RTO CONS: RTT:is not match the require 2site:3needed BACKUP hradware: CONS RISK : sigle point \ BACKUP'S policy SO BE

JLF_VMWOptions: AD

This question generates doubts because if you gonna work with vsan Stretched Cluster, the answer is A and D, BUT, ¿where it says you should work with Stretched Cluster?