A financial services company is deploying a distributed graph database for fraud detection on a fleet of Amazon EC2 instances. The graph database nodes require low-latency and high-throughput node-to-node network communication to synchronize transaction states. Additionally, client traffic is routed to the database nodes on port 8443 via a Network Load Balancer (NLB), while a custom health monitoring daemon runs on each instance on port 8080. Which combination of configuration steps should a solutions architect take to meet these requirements?
- ADeploy the EC2 instances within a spread placement group. Configure the Network Load Balancer target group to perform health checks using port 8080.
- BDeploy the EC2 instances within a cluster placement group. Configure the Network Load Balancer target group to perform health checks using port 8443.
- Deploy the EC2 instances within a cluster placement group. Configure the Network Load Balancer target group to perform health checks using port 8080.Cevap
- DDeploy the EC2 instances within a partition placement group. Configure the Network Load Balancer target group to perform health checks using port 8443.
Cevap
Deploy the EC2 instances within a cluster placement group and configure the Network Load Balancer target group to perform health checks using port 8080.
Deploying the EC2 instances in a cluster placement group packs them close together within a single Availability Zone, enabling low-latency, high-throughput node-to-node communications. Configuring the health check on port 8080 ensures that the Network Load Balancer correctly queries the dedicated health monitoring daemon rather than the database service port, preventing healthy instances from being falsely marked as unhealthy.
Adım Adım Çözüm
Anahtar Kavram
Selecting cluster placement groups for low-latency node-to-node communication and aligning NLB health check ports with custom monitoring daemons.