During the deployment of a Broker VM in a high availability (HA) environment, after configuring the Broker VM FQDN, an XDR engineer must ensure agent installer availability and efficient content…

Question

Options

• AUse shared SSL certificates and keys for all Broker VMs and configure a single IP address for
• BUpload the-signed SSL server certificate and key and deploy a load balancer
• CDeploy a load balancer and configure SSL termination at the load balancer
• DEnable synchronized session persistence across Broker VMs and use a self-signed certificate and

• A
  3% (1)
• B
  84% (31)
• C
  5% (2)
• D
  8% (3)

Explanation

Uploading a signed SSL server certificate and key - combined with deploying a load balancer - directly addresses both requirements in the scenario: the load balancer ensures agent traffic is distributed across Broker VMs and maintains connectivity during failovers, while a properly signed (trusted CA) certificate guarantees that agents can authenticate and download installers without certificate trust errors.

Why the distractors fail:

• A is wrong because configuring a single IP address undermines HA - you need a load balancer VIP, not a static single point of failure, regardless of shared certificates.
• C is wrong because SSL termination at the load balancer means Broker VMs receive unencrypted traffic internally, which breaks the end-to-end trust model that agents rely on; the certificate must reside on the Broker VM itself.
• D is wrong because self-signed certificates are not trusted by default by deployed agents, causing installer download failures - and session persistence alone does not solve the distribution and failover problem.

Memory tip: Think "LB + Signed = HA Aligned" - the Load Balancer handles traffic failover, and the Signed certificate handles agent trust. If either is missing or substituted (self-signed cert, single IP, LB termination), one of those two pillars collapses.

No community discussion yet for this question.