Generate a Chargeback report in Deep Security manager Web console.

All the choices listed here are valid.

Use the Representational State Transfer (REST) API to collect usage data from the tenants.

Monitor usage by the tenants from the Statistics tab in the tenant Properties window.

The incorrect port was used. The correct command would be: dsa_control -a dsm://server1.acme.com:4118

Deep Security Agents can not be activated through the Command Prompt. They must be activated through the Deep Security Manager Web console or through a deployment script.

The command listed can only executed from the Command Prompt on the Deep Security Manager computer.

"Allow Agent-Initiated Activation" is currently not enabled in Deep Security Manager.

The administrator could check the Multi-Tenancy log file for resource consumption details.

The administrator could generate a Tenant report from within the Deep Security Manager Web console.

The administrator will not be able retrieve this information without licensing and ena-bling the Multi-Tenancy Chargeback module in the Deep Security Manager Web con-sole.

The administrator downloads the Tenant usage details from the Deep Security Agent on the Tenant computer.

The Deep Security Notifier is a application in the Windows System Tray that displays the Status of Deep Security Manager during policy and software updates.

The Deep Security Notifier is a server components that collects log entries from man-aged computers for delivery to a configured SIEM device.

The Deep Security Notifier is a server component used in agentless configurations to allow Deep Security Manager to notify managed computers of pending updates.

The Deep Security Notifier is a application in the Windows System Tray that com-municates the state of Deep Security Agents and Relays to endpoint computers.

Any document files that display suspicious behavior will be submitted and executed in a sandbox environment on a Deep Discover Analyzer device.

Deep Security Agents using this Malware Scan Configuration will not monitor for compromised Windows processes.

Deep Security Agents will only be able to identify malware in files by using patterns downloaded from the Smart Protection Network.

Internet access is required to properly enable the features identified in this configuration.

Firewall rules using the Allow action always have a priority of 4.

Firewall rules using the Allow action can be assigned a priority between 0 and 4.

Firewall rules using the Allow action can be assigned a priority between 1 and 3.

Firewall rules using the Allow action always have a priority of 0.

In the example displayed in the exhibit, no activation code was entered for Application Control. Since the Protection Module is not licensed, the corresponding settings are not displayed.

These settings are used when both an host-based agent and agentless protection are available for the virtual machine. Since Application Control is not supported in agentless installations, there is no need for the setting.

In the example displayed in the exhibit, the Application Control Protection Module has not yet been enabled. Once it is enabled for this virtual machine, the corresponding settings are displayed.

In the example displayed in the exhibit, the VMware Guest Introspection Service has not yet been installed. This service is required to enable Application Control in agentless installations.

GET

PUT

VIEW

POST

Both 32-bit and 64-bit Deep Security Agents can be promoted to a Deep Security Relay.

Deep Security Agents promoted to Deep Security Relays no longer provide the security capabilities enabled by the Protection Modules.

Deep Security Relays are able to process Deep Security Agent requests during updates.

Deep Security Agents communicate with Deep Security Relays to obtain security up-dates.