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
A
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.