* Intra-zone traffic:On SRX devices, traffic between interfaces in the same security zone is allowed without requiring a security policy(Option C is correct). Policies are only evaluated for inter-zone traffic.
* Junos-host functional zone:This zone is a predefined functional zone that allows administrators to apply policies controlling access to the SRX firewall itself, such as SSH, HTTP, or SNMP traffic (Option D is correct).
* Null zone:This zone is a predefined discard zone. Interfaces placed in the null zone drop all traffic. It does not allow policy logging of dropped control plane traffic (Option A is incorrect).
* Management functional zone:This is used to define management interfaces, not the "functional zone" as stated in Option B (incorrect wording).
Correct Statements:C and D
Reference:Juniper Networks -Security Zones and Functional Zones, Junos OS Security Fundamentals.

Security policies on SRX support several actions:
* Permit:Allows traffic to pass according to the rule.
* Deny:Silently drops the traffic without notifying the source.
* Reject:Drops the trafficand sends a TCP RST (for TCP) or ICMP unreachable (for UDP/other protocols)back to the source. This provides feedback to the sending host.
* Next-policy:Allows policy chaining to evaluate the next policy set.
Therefore, the action that causes traffic to drop and a message to be sent to the source isreject.
Reference:Juniper Networks -Security Policy Actions, Junos OS Security Fundamentals.

Juniper Secure Connect client software is supported on the following three operating systems:
Windows 7, Windows 10, and macOS. For more information, please refer to the Juniper Secure Connect Administrator Guide, which can be found on Juniper's website. The guide states: "The Juniper Secure Connect client is supported on Windows 7, Windows 10, and macOS." It also provides detailed instructions on how to install and configure the software for each of these operating systems.

The session shows the internal host 10.10.101.140 translated to the public address
203.0.113.199 with its source port changed from 53726 to 21421, indicating source NAT with Port Address Translation (PAT).

You must allow ICMP under the host-inbound-traffic setting for the zone so that the SRX device itself can respond to ping requests.
The interface must be assigned to a security zone; if it's not part of any zone, traffic to or from that interface (including ping) will be dropped by default.