The intranet connection method provided by GaussDB (for Redis) is applicable when the application is deployed on the elastic cloud server, and the elastic cloud server and the database instance are…

Question

Options

• AIntranet IP
• BIntranet domain name
• CReverse proxy address
• DLoad balancing address

• A
  4% (1)
• B
  9% (2)
• C
  4% (1)
• D
  83% (19)

Explanation

Option D is wrong because GaussDB (for Redis) does not offer a load balancing address as an intranet connection method within the same VPC; load balancing addresses are associated with different service configurations and are not exposed as a direct connection option for this type of intranet access. Options A (Intranet IP) and B (Intranet domain name) are both valid because GaussDB (for Redis) supports direct connection via the instance's private IP address or a DNS-resolvable domain name that maps to that internal endpoint. Option C (Reverse proxy address) is also valid because GaussDB (for Redis) supports connecting through a reverse proxy, which sits in front of the database and forwards requests, and this is a documented intranet connection method. To remember this, note that the three valid methods all route traffic directly or indirectly to the instance within the VPC, while a load balancing address implies distributing traffic across multiple backend resources in a way that is not part of GaussDB (for Redis) intranet connection options.

No community discussion yet for this question.