2 Compliance clock is out of sync with the autocommit function. (the question didn't specify that this was compliance mode so this answer is bogus)
3 Offset time for autocommit has been met
4 Manual commit must be used for all compliance Smartlock directories. (nope, not true, and again the question didn't specify compliance mode)
Answers number 1 would be correct. If the autocommit is 30 minutes, when the file is closed you start counting up to 30 minutes. If 15 minutes in you try and delete or modify a file, you'll be able to, because 30 minutes have not yet elapsed.
1. Perform an in-place upgrade of the standard cluster to a compliance mode cluster.
2. SmartFail two of the nodes and use them to build a new compliance node cluster. (nope, you need 3 nodes to build a new cluster, and you'd need extra IB switches too, because you cannot share a backend IB network across 2 clusters)
3. Add the Smartlock license to the existing cluster and create some compliance mode directories. (nope, compliance mode directories cannot exist on a cluster that itself is not in a compliance mode)
4. Purchase a new cluster as there is no way to upgrade an existing cluster or reformat nodes.
This one is a bit trickier depending on your goals. If you want to go by-the-book, then Answer 4 is correct, you must either reformat the cluster (erasing all data), and start over in compliance mode, or buy a new cluster. Answer 1, however? There is a way for EMC Professional Services only to do this, but it's not done very often, and probably requires an RPQ from Engineering.
Nirvik
15 Posts
1324
0
Posted March 31st, 2017 06:00
Any expert here ? Who can help to answer above questions?