Consul Connect configuration in multi datacenter setup with Vault provider

Currently I am working on setting up Consul clusters in multi datacenter setup with Connect enabled while using Vault provider.

Consul 1.6.2

We have a `root-pki` and we setup two PKI for connect `consul-connect-west-pki` and `consul-connect-east-pki`.

Connect configuration on the primary datacenter:
```json
{
"connect": {
"ca_config": {
"address": "https://our-vault-address",
"intermediate_pki_path": "consul-connect-west-pki",
"root_pki_path": "root-pki",
"token": "REDACTED"
},
"ca_provider": "vault",
"enabled": true
}
}
```
Connect configuration on the secondary datacenter:

```json
{
"connect": {
"ca_config": {
"address": "https://our-vault-address",
"intermediate_pki_path": "consul-connect-east-pki",
"root_pki_path": "root-pki",
"token": "REDACTED"
},
"ca_provider": "vault",
"enabled": true
}
}
```

Is this the right approach? Or should I set `root_pki_path` for the secondary datacenter to point to the primary PKI? like:
```json
{
"connect": {
"ca_config": {
"address": "https://our-vault-address",
"intermediate_pki_path": "consul-connect-east-pki",
"root_pki_path": "consul-connect-west-pki",
"token": "REDACTED"
},
"ca_provider": "vault",
"enabled": true
}
}
```