01. Two arrays were installed with the same procedure, run the same firmware, and sit on the same network. One offers a replication feature in its interface and the other does not.
What most likely explains the difference?
a) The two arrays carry different licenses, so the feature is enabled only where its license is installed and active.
b) The feature is disabled automatically on any array as soon as it joins a production network.
c) The array lacking the feature runs a newer firmware build, so the capability was dropped in that release and cannot be surfaced.
d) The missing feature is evidence that the second array's installation procedure failed almost entirely and left the whole system misconfigured.
02. A configuration change must be completed with no loss of host access, but it affects a resource that part of the production workload currently depends on.
What is the soundest way to plan the work?
a) Start the change right away and monitor host error counters, rolling it back only if applications actually begin to fail during the operation.
b) Defer the change until a period of zero workload so that resource dependencies no longer matter, even if that delays the work indefinitely.
c) Disable the dependent workload's error reporting, suppress its path alerts and treat any transient events during the change as expected noise.
d) Map which workloads depend on the affected resource, confirm a redundant path can carry their I/O throughout, and sequence the change so that coverage is verified before it begins.
03. While planning parity-group layout for a system expected to grow, an administrator weighs building a few very large groups against building more numerous smaller ones.
Which consideration legitimately informs that layout decision?
a) Keeping every parity group as large as it can physically be made, on the principle that larger groups are simply always preferable for every kind of workload the array will ever be asked to host.
b) Ensuring each group holds the same number of logical volumes, since a uniform volume count is required across all groups.
c) How the chosen grouping affects both room for orderly future expansion and the operational cost of a rebuild should a drive fail.
d) The layout that consumes the fewest drives overall, since minimizing total drive count is the primary objective of any grouping decision.
04. The array hardware has been physically installed and powered on. Before any application host can store data on it, which of the following must occur?
a) The raw drive capacity must be organized into protected storage and then into host-presentable volumes.
b) The array must be filled to its full capacity before the first usable volume can be presented to a host.
c) Every drive must be formatted individually and then claimed by the host application before any volume can be addressed.
d) Each host must be physically relocated to a rack adjacent to the array before it can address any storage.
05. Which situation most clearly calls for capturing a fresh configuration backup?
a) Only after a failure has already disrupted the array's operation.
b) Only once, at the moment the array is first installed, and never again afterward.
c) Just before making a significant configuration change to the array.
d) Never, as long as the array continues operating normally.
06. One technician must change configuration settings on the array, while a colleague only needs to watch for health and performance alerts. Which statement best reflects how the management software supports both needs?
a) Each task needs its own separate and unrelated product, with no shared management framework connecting them.
b) Centralized management supports both configuration and monitoring, so each person uses the capability suited to their task within the same framework.
c) Configuration changes must all be made through the Remote Ops Monitor Agent, which is also the component that handles every monitoring task for the system.
d) Monitoring requires reinstalling the array each time, while configuration can only be done directly through firmware settings.
07. After reviewing the system status and alert detail for a reported fault, an engineer still cannot tell whether the symptom comes from a degraded host path or from a failing array component.
What is the most appropriate next step to isolate the cause?
a) Replace the array component named in the alert right away, treating a successful swap as confirmation that it was the cause.
b) Reboot the affected hosts one by one until the symptom clears, then treat the last host rebooted as the faulty element.
c) Determine whether the symptom follows one host path or persists across all of them.
d) Suppress monitoring on the suspected component so the repeated alerts stop while normal operation is observed.
08. Host ports are healthy and all drives are reachable, yet the two controllers are failing to coordinate and an HA takeover did not complete. Which subsystem is the most appropriate first place to investigate?
a) The back-end connectivity between the controllers and the drives
b) The front-end channel boards
c) The redundant power supplies
d) The internal controller-to-controller fabric
09. During an online configuration change, which characteristic of the operation is what actually allows host I/O to continue uninterrupted?
a) The change is written only to a backup copy and then merged into the live configuration at the next array restart.
b) The change is applied while the data paths the hosts rely on keep serving I/O, so no path they depend on is ever taken down.
c) Every host connection to the array is briefly dropped and then re-established afterward, so that the newly applied configuration can be loaded cleanly and consistently across all of the attached paths.
d) The hosts are quiesced for the duration of the change and automatically resume their I/O once it has completed.
10. Following a component failure and replacement, the array's configuration must be returned to its pre-failure state. The success of this recovery depends most directly on what?
a) Whether the failed component was returned to the vendor and logged against the open support case before recovery began.
b) Whether the production hosts remained powered off for the entire duration of the failure window.
c) Whether the replacement component is physically larger than the original part it replaced.
d) Whether a recent, verified configuration backup of the pre-failure state exists.