diff --git a/tidb-cloud/setup-self-hosted-kafka-pls.md b/tidb-cloud/setup-self-hosted-kafka-pls.md
index 4b33d96c59e27..c266cc6a8ce2e 100644
--- a/tidb-cloud/setup-self-hosted-kafka-pls.md
+++ b/tidb-cloud/setup-self-hosted-kafka-pls.md
@@ -616,3 +616,15 @@ b3.usw2-az3.abc.us-west-2.aws.3199015.tidbcloud.com:9095 (id: 3 rack: null) -> E
    - Bootstrap Ports: 9092. PS: only one port is fine since we configure a special bootstrap target group behind this port.
 3. Continue follow the guideline in [To Kafka Sink](/tidb-cloud/changefeed-sink-to-apache-kafka.md)
 4. If everything go fine, you will successfully finish the job.
+
+## FAQ
+
+### How to connect to the same Kafka private link service from two different TiDB Cloud projects?
+1. Let's say you have already follwoing the above document successfully setup the connection from the first project.
+2. You want to setup the second connection from the second project.
+3. Go back to the head of this document proceed from begining. When you proceed to the "First, Setup Kafka Cluster" section. Follow the "Reconfigure a Running Kafka Cluster" section, create another group of EXTERNAL listener and advertised listener, you can name it as EXTERNAL2. Please notice that the port range of EXTERNAL2 can not overlap with the EXTERNAL.
+4. After brokers reconfigured, you add another group of target groups in LB, including bootstrap and brokers target groups.
+5. Proceed TiDB Cloud connection with 
+   - New Bootstrap port
+   - New Kafka Advertised Listener Group
+   - The same Endpoint Service