When configuring mobile and remote access on Cisco VCS Control, what are two required configuration steps? (Choose two.)

Provisioning is an optional feature for device configuration deployment and is not a required step for enabling the Mobile and Remote Access traversal path itself.

All Cisco VCS systems must be synchronized to a reliable NTP service because MRA relies on TLS certificates and token-based authentication that are time-sensitive; clock skew between nodes can cause certificate validation failures and authentication errors.

The system hostname and domain name must be correctly specified because the VCS uses them to generate its server certificate's CN and SAN fields, which are validated by endpoints and Expressway peers during TLS handshake for MRA traversal.

Local DHCP server specification is not a configuration requirement on the VCS Control for MRA; DHCP is managed at the network infrastructure level and is not configured within VCS.

The Unified Communications mode on VCS Control must be set to 'Mobile and remote access', not 'peer-to-peer'; peer-to-peer mode does not enable the MRA traversal functionality.