An administrator is creating a vApp for a multi-tiered web application…

Click the Exhibit button.

An administrator is creating a vApp for a multi-tiered web application. The vApp has been as shown in exhibit. Testing of the vApp indicates that attempts to communicate with the web server on Dev_Web_01 fail.

A.
Change the startup sequence to startup when VMware Tools is ready

B.
Change the Startup Sequence value from 120 to 240

C.
Move the Dev_Web_01 virtual machine to Group 3

D.
Move the Dev_SQL_01 virtual machine to Group 2 and move the Dev_App_01 virtual machine to Group 3

Explanation:

The only logical answer seems to be A. Since option B is asking you to increase the time elapsed which has no impact on the virtual machine.
There is also no use moving Dev_Web_01 to group 3 or even moving or shuffling the virtual machines from one group to another.

14 Comments on “An administrator is creating a vApp for a multi-tiered web application…

  1. Matt says:

    I believe the correct answer here is “C. Move the Dev_Web_01 virtual machine to Group 3.”

    A likely reason the web application (the front-end) is unreachable is due to the Dev_SQL_01 server (the back-end) still loading.

    By placing Dev_Web_01 and Dev_SQL_01 in the same Start Order group, they will power-on at exactly the same time. Ticking the option “VMware Tools are ready” will only allow a VM to start before the specified delay. Starting Dev_Web_01 earlier than it already is (not possible in this scenario as its already powering on immediately) would only cause more connectivity issues, not less.

    Moving Dev_Web_01 to Group 3 will ensure that Dev_Web_01 & Dev_App_01 have had amble time to power-on and start their services before the web application loads.

    1. Matt says:

      ***Correction***

      Moving Dev_Web_01 to Group 3 will ensure that *Dev_SQL_01* & Dev_App_01 have had amble time to power-on and start their services before the web application loads.

      ***Correction***

      I believe the correct answer here is “C. Move the Dev_Web_01 virtual machine to Group 3.”

      A likely reason the web application (the front-end) is unreachable is due to the Dev_SQL_01 server (the back-end) still loading.

      By placing Dev_Web_01 and Dev_SQL_01 in the same Start Order group, they will power-on at exactly the same time. Ticking the option “VMware Tools are ready” will only allow a VM to start before the specified delay. Starting Dev_Web_01 earlier than it already is (not possible in this scenario as its already powering on immediately) would only cause more connectivity issues, not less.

      Moving Dev_Web_01 to Group 3 will ensure that Dev_SQL_01 & Dev_App_01 have had amble time to power-on and start their services before the web application loads.

  2. admin says:

    Thanks your explanation, Matt. I also thought that Moving Dev_Web_01 to Group 3 is the good way. However, the option “VMware Tools are ready” is different with the specified delay. And it is more simple than moving Dev_Web_01 to Group 3, just clicking Dev_Web_01 and stick checkbox “VMware Tools are ready”.
    How do you think?

    “Well… create a vApp, add the Domain Controllers, DNS servers and Exchange Mailbox Server, as well as the Exchange CAS server (just drag and drop them in the vCenter console). Edit the vApp’s settings and you’ll find a tab called “Start Order”. Now, here you’ll find some “Groups” and all of the VM’s you added are probably listed in their own group. Make sure that your VM’s are listed in the correct order (use the up and down arrows), so that Domain Controllers at the top, and the mailbox server at the bottom in this case. Now, if you put two machines in the same group, they’ll boot at the same time, otherwise it’s a top to bottom list (and reverse for shut down). My preference here is to change the settings for each VM so that the next machine will boot once VMware tools has loaded in the VM, so, tick the “VMware Tools are ready” check box. Whilst you’re doing this, set the “Shutdown Action” to “Guest Shutdown”.”

    Source:
    http://danielhayward.wordpress.com/2011/03/01/vapps-in-vsphere-4-and-why-theyre-very-very-useful/

    1. vspheremat says:

      Admin, generally you’re right, but not in context of this exam question. You have only one option to fix the problem here. And the main problem of the shown three-tier application is the startup order. The first and the third tier boot in parallel (are in the same group) and they boot before the second tier. To guarantee the start order dependencies between the tiers, you must first put Web tier to a third group (C). You can use “startup when VMware Tools is ready” as a second step to reduce delays between tiers, but this option alone does not fix the ordering problem.

  3. Ryan M says:

    I think A is the answer.

    Problem with B is that we don’t know that adding 120 seconds will be sufficient.

    Problem with C is that if we do that one action, moving the web server to a third group – then the startup order goes: SQL(group1), App(group2), Web(group3).

    Plus, other dumps indicate A

    1. Daniel says:

      Problem with C is that if we do that one action, moving the web server to a third group – then the startup order goes: SQL(group1), App(group2), Web(group3).

      -> but thats what sould solve the problem.

      Sumps: A LOT of them are just PLAIN wrong.

  4. JC says:

    I vote A, since the vmware tools ready indicator will be the one that may guarantee that the VM power on was OK.

    note that moving the vm to another group won’t solve the problem, since it won’t guarantee that the first vm on group one powered on successfully.

    you’re all assuming that the problem is that the vm powers on correctly but the SQL server service isn’t online and ready at the time the web vm powers on.

    note that if you move the web vm to group 3, and the sql server powers on but for some reason does not boot to the OS. the web vm won’t be able to communicate.

    hence, vmware tools ready is the only option that, at least, may tell that the OS started correctly.

  5. sajid shaikh says:

    I am agree with JC. option A (Change the startup sequence to startup when VMware Tools is ready) is the correct answer.

  6. delesc says:

    The idea is to have a working (multi-tier) App, which can be accessed using a web console.
    The web server is dependent on the application server for it to work. Without the application server having started, the web server cannot connect to it. So when the web services start up, they try to connect to the application server, and can’t, so they fail.

    Later, in the exhibit, the application server starts but that doesn’t fix the failed web server.
    You could THEN restart the web server, at which time it can connect to the (now running) application server and successfully start.

    Answer is C (you need to create a group 3, and move the web server to it)


Leave a Reply

Your email address will not be published. Required fields are marked *