Administration of Blue Coat ProxySG 6.6 (Broadcom) Free Sample Questions

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.

The first rule in a layer that matches stops further rule processing in that layer, implementing a "first match wins" policy evaluation model. This ensures predictable policy behavior and prevents conflicting rules from being processed. Later rules are not evaluated once a match is found, and processing continues to the next layer if applicable. The other options incorrectly describe the rule evaluation process. Reference: https://origin-symwisedownload.symantec.com/resources/webguides/sgos/policy/Learn/aboutlayerandruleeval/layerguards.htm

CPL (Content Policy Language) components are organized in descending hierarchical order as: Layers (highest level containers), Rules (within layers), Conditions (within rules that define when rules apply), and Triggers (within conditions that specify the action to take). This hierarchical structure allows for organized and manageable policy configuration in the ProxySG.

A policy trace reports "N/A" when a rule is not reached during evaluation, typically because an earlier rule in the same layer already matched and stopped further processing, or because the conditions for reaching that rule were not met. This indicates the rule was not evaluated for the specific transaction being traced, not that it was disabled or nonsensical.