An administrator is attempting to create a protection policy while creating an SMB share however the option is not available. What is the reason?

Question

Options

• AThe protection policy has been previously associated with a file system
• BThe protection policy must be created before associating it with the volume resource
• CThe protection policy must be created before associating it with the file system
• DThe protection policy is only available with file level retention enabled

• A
  2% (1)
• B
  7% (3)
• C
  89% (41)
• D
  2% (1)

Explanation

Option C is correct because SMB shares are built on top of file systems - the protection policy must be applied at the file system level before any shares are created on it. When you're in the SMB share creation wizard, the system expects the underlying file system to already have its protection policy in place; since that prerequisite is missing, the option is simply unavailable.

Why the distractors are wrong:

• A is backwards - a policy already associated with a file system would mean it is available, not that it's blocked.
• B swaps the wrong resource; protection policies for SMB environments apply to file systems, not volumes (which are block storage constructs).
• D conflates two separate features; file level retention (WORM) and protection policies (snapshot/replication schedules) are independent - you don't need one to use the other.

Memory tip: Think of the stack from bottom to top - Policy → File System → Share. You can only configure things at a higher layer once the lower layers are properly set up. If the file system has no policy yet, the share creation screen has nothing to inherit.

No community discussion yet for this question.