Functionalities supported for Asynchronous FPolicy management. (choose TWO)

File-access blocking requires synchronous FPolicy because the ONTAP node must hold the client's file request open and await a permit or deny response from the FPolicy server before the operation can proceed.

File archiving and hierarchical storage management in this context require synchronous FPolicy because the server must intercept operations and redirect or stage data before the operation completes, which asynchronous mode cannot enforce.

Asynchronous FPolicy supports file-access auditing because notifications are sent to the external FPolicy server after the client operation has already completed, making it well-suited for generating audit trails and access logs without blocking file operations.

Encryption and decryption are not FPolicy functions at all; they are handled by ONTAP's native storage encryption features such as NetApp Volume Encryption and NetApp Storage Encryption.

Compression and decompression are storage efficiency operations managed by ONTAP's data reduction engine, not by FPolicy, and cannot be delegated to an external FPolicy server in either mode.

Storage resource management is supported in asynchronous mode because it involves monitoring and classifying file system activity after the fact, and does not require the FPolicy server to intervene before an operation is allowed to complete.