Which of the following is NOT listed as a consideration when designing a subnet's VM?

• A. Supported assets
• B. Contract capabilities
• C. Security policies
• D. Network latency

Answer: (D)

When you design a subnet's VM, you decide what assets it will support, what contract capabilities it will expose, and what security policies it will enforce. These choices define the VM’s functionality and safety — what tokens or assets can be processed, what types of smart contracts it can run (such as EVM-compatible or WASM-based code), and how access and operations are controlled.

Network latency, while crucial for performance and user experience, is not a design feature you configure inside the VM itself. It’s an operational factor determined by the network topology, validator distribution, and routing, not by the VM’s capabilities or security settings. So latency isn’t a design consideration for the subnet VM, making it the correct choice.