HPE0-J58 Designing Multi-Site HPE Storage Solutions

Loading demo links...

Showing 1–3 of 10 questions

Question 1

A customer has two sites. The link between sites is Fibre Channel, and the distance between sites is less than 1km. The link latencies are within HPE recommended tolerances.

The customer asks you to design a Peer Persistent solution using HPE servers running physical Windows 2016 servers and HPE 3PAR storage.

What are characteristics of the Quorum Witness? (Select two.)

Select all that apply, then click Submit answer.

  • A virtual implementation of the Peer Persistence Quorum Witness is required on a third site

  • A Peer Persistence Quorum Witness is required for normal HPE 3PAR Peer Persistence operation

  • The Quorum Witness initiates the fail-over, passing control to the standby array

  • A physical implementation of the Peer Persistence Quorum Witness is required on a third site

  • Quorum Witness becomes relevant only during 3PAR Peer Persistence failover

Question 2

You are designing an HPE 3PAR replication solution for a customer in a metropolitan area that includes two main sites and a third disaster recovery site. The main sites will be in synchronous replication. The disaster recovery site can be asynchronously replicated. What are two points you should highlight to the customer? (Select two.)

Select all that apply, then click Submit answer.

  • Tertiary site volume paths are active/read only

  • Quorum Witness at the third site enables automatic failover to tertiary site

  • Secondary site volumes paths are active/optimized read/write

  • Quorum Witness at the third site enables automatic failover to the secondary site

  • Primary site volumes paths are standby read/write

Question 3

A startup company is considering an HPE Nimble solution. They have a small IT budget, and they need to be future-proof for changing performance requirements. How does the Nimble architecture meet the company needs? (Select two.)

Select all that apply, then click Submit answer.

  • native support for block and file services

  • minimal downtime technology refresh

  • Support for FCoE

  • non-disruptive technology refresh

  • ability to mix-and-match All flash and hybrid nodes