101 · Question #377
In order to ensure that a specific file type is never moved down to a secondary file tier, the administrator should:
The correct answer is C. Set a policy that the file type remains on primary storage. ARX supports policy-based tiering that allows administrators to pin specific file types to primary storage, preventing automatic migration to a secondary tier.
Question
In order to ensure that a specific file type is never moved down to a secondary file tier, the administrator should:
Options
- ASet up an automated bot that accesses that file once a week.
- BThis is not possible on the ARX.
- CSet a policy that the file type remains on primary storage.
- DInstruct the end users to put the file in a non-tiered directory.
How the community answered
(27 responses)- A4% (1)
- B11% (3)
- C81% (22)
- D4% (1)
Why each option
ARX supports policy-based tiering that allows administrators to pin specific file types to primary storage, preventing automatic migration to a secondary tier.
Periodically accessing a file may update its last-accessed timestamp but does not enforce a retention policy - the ARX could still migrate the file based on other configured criteria.
This is factually incorrect because ARX does support policy-based tiering controls that can explicitly prevent specific file types from being moved to secondary storage.
ARX's policy engine allows administrators to define rules based on file type, ensuring certain file types are always retained on primary storage and never demoted. When the policy is applied, the ARX enforces it for every matching file, overriding any default tiering behavior that would otherwise migrate the file to a secondary tier.
Placing files in a non-tiered directory requires manual end-user action and bypasses ARX's built-in policy engine, making it an unmanaged and unreliable workaround.
Concept tested: ARX policy-based file tiering prevention
Source: https://support.f5.com/csp/product/arx
Topics
Community Discussion
No community discussion yet for this question.