Consul 1.15 Multi Datacenter Federation Practice Question
A cross-datacenter service discovery request is failing. You observe the local datacenter can resolve the service via DNS, but the remote datacenter cannot. Which configuration parameter must be checked?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
primary_datacenter
The 'primary_datacenter' and 'allow_stale' settings are crucial, but cross-DC discovery often fails if the 'enable_local_script_checks' or specific WAN gossip configurations prevent cross-link visibility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
enable_central_config
Why it's wrong here
This manages config entries, not cross-DC discovery.
- ✗
node_meta
Why it's wrong here
Node metadata does not impact discovery resolution.
- ✓
primary_datacenter
Why this is correct
The primary_datacenter must be correctly defined for ACL and gossip coordination across the federation.
- ✗
check_ttl
Why it's wrong here
TTL checks are local to the node.
Visual reference
About these practice questions
This Consul 1.15 question is part of Courseiva's 194-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official HashiCorp exam blueprint
This Consul 1.15 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Consul 1.15 exam.