The Secure Client user tries to connect to a host in Detroit’s domain. Because Detroit is a Policy Server…

In the following graphic, the remote Secure Client machine does not have an installed Desktop
Policy. The Secure Client user tries to connect to a host in Detroit’s domain. Because Detroit is a
Policy Server.

In the following graphic, the remote Secure Client machine does not have an installed Desktop
Policy. The Secure Client user tries to connect to a host in Detroit’s domain. Because Detroit is a
Policy Server.

A.
It will initiate explicit login and attempt to install a Desktop Policy on the Secure Client machine,
before it allows a connection to its domain.

B.
It will initiate implicit login and attempt to install a Desktop Policy on the Secure Client machine,
before it allows a connection to its domain.

C.
It will initiate implicit login only, before it allows a connection to its domain.

D.
It will initiate explicit login only, before it allows a connection to its domain.

E.
It will initiate implicit login and attempt to install a Desktop Policy on the SecuRemote machine,
before it allows a connection to its domain.

Explanation:

: the implicit login occurs when a secure client does not have a security policy installed and tries to
communicate through a policy server. The policy server will attempt to install a policy on the
desktop. This is initiated by the policy server. See Page 12.19 of CCSE NG Official Courseware.
(VPN1-FW1 Management II NG FP-1) . See also “Figure 9” on the same domain.



Leave a Reply 0

Your email address will not be published. Required fields are marked *