250-430 Administration of Blue Coat ProxySG 6.6 (Broadcom) Practice Questions

A destination IP address is NOT a component of a proxy service listener because proxy service listeners define where the ProxySG listens for incoming connections, not where traffic is destined. Proxy service listeners typically include components like listening IP address, port, and protocol, but the destination is determined by the client request or policy rules, not by the listener configuration itself.

Inline deployment represents a single point of failure because all network traffic must pass through the ProxySG appliance. If the ProxySG becomes unavailable, network connectivity is completely interrupted. Other deployment methods like explicit proxy or WCCP provide alternative paths for traffic when the proxy is unavailable, but inline deployment creates a critical dependency on the appliance for all network access. Reference: https://www.symantec.com/content/dam/symantec/docs/white-papers/swg-deployment-methodologies-en.pdf

The SSL Proxy is used to specify which traffic should be encrypted by intercepting and decrypting SSL/TLS connections for inspection, then re-encrypting them before forwarding to the destination. This allows the ProxySG to apply security policies to encrypted traffic while maintaining end-to-end encryption from the client perspective.

The ProxySG performs a hash against the URL of the object and uses the hash as the basis for a lookup into the table of cached objects. This hash-based approach provides efficient and consistent object location within the cache structure. Using hostname alone would be inefficient for large caches, using only the first 32 bytes would not provide sufficient uniqueness, and the other options do not accurately describe the ProxySG cache lookup mechanism.

Without surrogate credentials, transparent proxy users would have to reauthenticate for each domain they access because the ProxySG would not be able to impersonate the user for subsequent authentication requests to different backend servers. Surrogate credentials allow the ProxySG to authenticate on behalf of the user to multiple domains without requiring repeated authentication prompts. The other options are incorrect because authentication would still be possible, and surrogate credentials are specifically needed for transparent proxy scenarios. Reference: https://origin-symwisedownload.symantec.eom/resources/webguides/proxysg/6.6/reverse_proxy_webguide/Content/Topics/Tasks/Authentication/surrogate_credentials_co.htm

When disk space is full on a ProxySG, policy tracing becomes unavailable because tracing requires disk space to store the trace files and logs. The ProxySG prioritizes core proxy functionality over diagnostic features when storage is constrained. Health checks, event logs, and normal operations continue to function as they require minimal disk space, but policy tracing generates significant data that requires available storage.