PrepAway - Latest Free Exam Questions & Answers

How can the administrator achieve this task without any downtime to the application?

A system administrator has deployed an application. The development team has updated a new
version of this application. The administrator needs to immediately deploy this updated application
and guarantee that only this new edition is used by clients and that any service requests for the
application are queued during the deployment of the new application.
How can the administrator achieve this task without any downtime to the application?

PrepAway - Latest Free Exam Questions & Answers

A.
Perform a soft rollout.

B.
Perform a hard rollout.

C.
Perform an atomic rollout.

D.
Perform a concurrent activation rollout.

41 Comments on “How can the administrator achieve this task without any downtime to the application?

  1. certhunt says:

    Use group rollout to replace editions on members of the target cluster in a group of one. Group rollout is the most typical choice, and is useful when the cluster contains four or more members. Alternatively, you can perform group rollout with a specified group size through scripting. For more information about group rollout, read about application edition management administrative tasks. When the new edition becomes available during group rollout, all requests are directed to the new edition.

    Use atomic rollout to replace one edition with another on half of the cluster at a time. This rollout type serves all user requests with a consistent edition of the application. Because all user requests are served a consistent edition, your cluster runs at half capacity. If your cluster has four or more members, consider dividing up the cluster into smaller groups by performing a group rollout. Atomic mode is also used with a single server deployment target. In a single server deployment target, the actions that are carried out against the second half of the cluster are omitted. If you stop your deployment targets before you start atomic rollout, the deployment targets are started when the new edition replaces the active edition regardless of the reset strategy you choose. This procedure provides better availability to the requests that are serviced during the rollout period.

    Reset Strategy

    Soft reset will restart only the application .If no native libraries is used by your application soft reset is enough.

    Hard reset will restart the application server so the native files as well can be loaded if needed by your application.




    0



    0
    1. Himanshu says:

      Sir,

      I am fresher and according to company rolls i have to pass this exam to have project on WAS administration. Can you please reply your email id or any contact that i can be in touch with you. Sir really need correct answer please its about my money and future both.My mail id is hhimanshuvyass@gmail.com




      0



      0
  2. RomanSL says:

    I think that correct answer is C, cause we have only two types of rollout – grouped and atomic.
    Soft and hard are not rollouts but resets.
    Atomic rollout is a most applicable option.




    0



    0
  3. Frank says:

    C is correct answer. https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cwve_xdappedalg.html

    Performing an atomic rollout activates the new edition on half of the cluster first, and then activates the edition on the remaining half of the cluster. While the first half of the cluster is taken offline and updated, application requests are routed to the second half of the cluster. Verify that half the cluster can handle the entire load during the rollout period.




    0



    0

Leave a Reply