Your SmartCenter Server fails and does not reboot. One of your remote Security Gateways managed by the SmartCenter Server reboots. What happens to that remote Gateway after reboot?

A.
Since the SmartCenter Server is not available, the remote Gateway cannot fetch the Security Policy.
Therefore, no traffic is allowed through the Gateway.

B.
Since the SmartCenter Server is not available, the remote Gateway cannot fetch the Security Policy.
Therefore, all traffic is allowed through the Gateway.

C.
The remote Gateway fetches the last installed Security Policy locally, and passes traffic normally. The Gateway will log locally, since the SmartCenter Server is not available.

D.
Since the SmartCenter Server is not available to the remote Gateway, fetching the Security Policy and logging will both fail.

E.
Since the SmartCenter Server is not available, the remote Gateway uses the local Security Policy, but does not log traffic.