01. Using its end-to-end topology view, Ops Center Analyzer traces a latency SLO breach to contention at a shared pool and pinpoints the volume responsible. The team now wants to enforce a per-LDEV I/O upper-limit to resolve the contention.
Which statement correctly describes how detection and enforcement are divided between the tools?
a) Analyzer detects and traces the bottleneck to the root resource, and RAIDCOM applies the LDEV upper-limit, because performance analysis and array configuration are separate roles
b) RAIDCOM both detects the bottleneck through its monitoring view and enforces the upper-limit
c) Protector enforces the QoS upper-limit once Analyzer flags the breach
d) Analyzer both detects the bottleneck and applies the I/O upper-limit to the LDEV directly
02. During a reported slowdown the administrator suspects a very brief port-saturation spike, but the standard dashboard reports, which are delivered within minutes of the events, show nothing unusual for that interval.
Which Analyzer capability is designed to expose a short-lived spike like this?
a) The E2E topology view, which maps the relationships between resources
b) Capacity forecasting, which uses historical consumption trends to project when additional capacity will be required
c) Trend reporting, which aggregates historical performance over longer intervals
d) Granular data collection, which gathers second-level data to reveal spikes the delayed dashboard reporting can miss
03. Inside a thinly provisioned pool, a number of allocated pages now contain only zeros after host-side activity, and that capacity is no longer doing useful work.
Which SVOS capability is designed to recover it?
a) Zero Page Reclaim
b) Dynamic Resizing
c) Adaptive Data Reduction
d) Dynamic Tiering
04. To avoid back-end hot-spots, an administrator wants a volume's I/O spread widely across many parity groups in a pool so that no single group becomes a bottleneck.
Which SVOS feature provides this through wide striping?
a) Adaptive Data Reduction
b) Zero Page Reclaim
c) Hitachi Dynamic Tiering
d) Hitachi Dynamic Provisioning
05. Ops Center Analyzer shows that one volume on a shared pool is sustaining very high IOPS and is starving the other volumes that share the pool. The other workloads must be protected.
Which QoS action directly addresses the problem?
a) Enable data compression on the pool to reduce its load
b) Apply an I/O upper-limit to the high-IOPS volume so it cannot exceed a set rate
c) Raise the priority of the high-IOPS volume
d) Increase the queue depth on all volumes in the pool
06. Analysis has identified a volume that should be held to an I/O ceiling. An administrator now needs to apply that upper-limit setting to specific LDEVs as part of the array's configuration, using a scriptable command-line interface.
Which tool performs this configuration step?
a) Ops Center Protector
b) Ops Center Analyzer
c) RAIDCOM (CCI)
d) Ops Center Automator
07. While a failed drive in a parity group is being rebuilt, host response time on that group's volumes rises and the group's back-end busy rate climbs, even though host IOPS to those volumes has not changed.
What is the best interpretation?
a) The host workload has increased during the rebuild window and is what is actually driving the higher back-end busy rate.
b) The rebuild is consuming the group's back-end bandwidth and competing with host I/O.
c) The front-end ports have become the bottleneck during the rebuild.
d) Cache hit ratio has improved, raising the busy rate.
08. Two parity groups serve comparable workloads. Group A shows higher IOPS than Group B, but Group B shows a much higher average queue length and response time than Group A.
Which group is closer to its performance limit, and why?
a) Group A, because IOPS is the only metric that reflects how loaded a parity group is.
b) Group A, because higher IOPS always means a drive is working harder and is therefore the one that must be closest to its performance limit.
c) Group B, because a rising queue length and response time show requests waiting on a saturating resource.
d) Neither, because queue length and IOPS are unrelated to a parity group's load.
09. Host latency is high. The metrics show MP utilisation at 40%, a high overall cache hit ratio, and low back-end disk utilisation and queue lengths across every parity group — but one front-end port is running at its maximum sustainable IOPS with elevated response time, and the affected hosts are all mapped through that port.
What is the correct conclusion?
a) Cache is too small for the working set, so it needs expansion to lift the hit ratio.
b) That single front-end port is the bottleneck; with the other layers healthy, redistributing those hosts across additional ports or paths is the remedy.
c) The drives are saturated, so the pool needs more spindles to clear the backlog.
d) The controllers are overloaded, so volume ownership needs rebalancing across them.
10. For one volume the readings are: cache hit ratio in its normal range; front-end port latency low with healthy throughput; and the backing parity group at a near-100% operating rate with a high average queue length and rising response time.
Which component is the bottleneck?
a) The front-end port, which is congested with host traffic.
b) The read cache, which is too small for the working set.
c) The controller processor, which is saturating on this volume.
d) The back-end parity group, which is saturated and queueing I/O.