Which two are true when creating a SyncMirror volume? (Choose two.)
Options:
A.
The disks selected for Plex 0 and Plex 1 must come from the same disk shelf.
B.
The disks selected for Plex 0 and Plex 1 must come from the same disk pools.
C.
The number of disks added must be an even number and equally divided between the two plexes.
D.
The disks are selected first on the basis of equivalent bytes per sector (bps) size, then on the basis of the size of the disk. If there is no equivalent-sized disk, Data ONTAP takes a larger capacity disk and right-sizes it.
The rules for the selection of disks or array LUNs, for using as mirrored aggregates, are as follows:
Disks or array LUNs selected for each plex must be in different pools.
The same number of disks or array LUNs must be in both the plexes.
Disks are selected first on the basis of equivalent bytes per sector (bps) size, then on the basis of the size of the disk.
If there is no equivalent-sized disk, Data ONTAP uses a larger-capacity disk, and limits the size to make it identically sized.
Data ONTAP names the plexes of the mirrored aggregate.
Question 2
What happens when two aggregates are rejoined?
Options:
A.
It is not possible to rejoin aggregates.
B.
Data ONTAP will always retain data from the newest aggregate.
C.
Both aggregates revert to the last common snapshot before the split.
D.
You will have a large new aggregate containing all volumes from both aggregates.
E.
One of the aggregates will be overwritten and you will lose any data changed on it after the split.
Answer:
E
Explanation:
Explanation:
When you rejoin split aggregates, Data ONTAP mirrors the data from one aggregate to the other and destroys data that existed on that aggregate before the rejoin.
Question 3
You have connected all cables and disk shelves in a fabric-attached MetroCluster. Which command would verify that disks are connected and have dual paths?
Options:
A.
disk show
B.
sysconfig -p
C.
vol status -r
D.
storage show disk -p
Answer:
D
Explanation:
Explanation:
The operator must ensure that the partner filer does not become operational at any time while a filer is in a takeover mode initiated by the use of this command