How does HPE OneView identify the revision of each resource when using REST APIs?

How does HPE OneView identify the revision of each resource when using REST APIs?
A. with an eTag for each resource
B. with a resource revision included in the SSH header
C. with a Uniform Resource Identifier (URI) for each resource
D. with direct access requests to the HPE OneView database

Download Printable PDF. VALID exam to help you PASS.

2 thoughts on “How does HPE OneView identify the revision of each resource when using REST APIs?

    1. An eTag is a code marking the current state of a resource. It is an opaque string/value indicating the current revision of the resource.

Leave a Reply

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


The reCAPTCHA verification period has expired. Please reload the page.