What are two features to consider when creating a named ACL? (Choose two.)

When creating a named Access Control List (ACL), two important features to consider are:

1. Be descriptive when creating the ACL name: This is crucial for ease of management and understanding. A descriptive name helps in quickly identifying the purpose and scope of the ACL. It should ideally reflect the function or the area of the network it is intended to control access for.
2. Use alphanumeric characters if needed: Employing alphanumeric characters in the ACL name can be beneficial for creating more specific or structured naming conventions. This can include using numbers for versioning or sequencing, and letters for easily distinguishing between different ACLs.

The other options provided are less relevant or not best practices for naming ACLs. For instance, using special characters like ! or * is generally avoided as they might not be supported in all systems and can lead to confusion. Modifying an ACL using a text editor is more about the process of editing an existing ACL rather than a consideration for initially naming it. While using a space for ease of reading is generally good advice for writing and documentation, in the context of ACL naming, spaces might not be supported, and even if they are, it’s usually better to use other methods like underscores (_) to separate words or concepts in names.