A Prometheus server is configured to scrape a node_exporter on a remote host. The target appears as 'DOWN' in the Targets page. The engineer can curl the node_exporter endpoint from the Prometheus server and get valid metrics. What is the most likely cause of the target being DOWN?

The node_exporter is exposing metrics in the wrong format.

The Prometheus server's firewall is blocking outbound connections to the exporter.

The scrape job's 'scrape_timeout' is set to 1s, which is too short for the exporter to respond.

The node_exporter is using a self-signed certificate that Prometheus does not trust.

A large organization has multiple independent Prometheus servers, each monitoring a separate data center. They want to create a central Prometheus that aggregates metrics from all these servers for a global view. They also want to ensure that if one data center's Prometheus is down, the central Prometheus still has the most recent data from the other data centers. Which approach is most appropriate?

Configure the central Prometheus to federate from each data center's Prometheus using the /federate endpoint.

Run a single Prometheus server that scrapes all targets in all data centers directly.

Use Alertmanager to aggregate alerts from all data centers and display them centrally.

Have each data center's Prometheus push all its metrics to the central Prometheus via the Pushgateway.

LPI DevOps Tools Engineer

Domain 4Objective 2

704.2 Prometheus Monitoring (weight: 6) DEVOPS-TOOLS-ENGINEER Practice Questions (Page 8)

Part of the 704 Security and Observability domain, which makes up ~26% of our current practice bank. Linux Professional Institute does not publish an official question count, but from its 90-minute exam (~35–60 total, ~9–16 in this domain), expect 2–4 from this objective — we provide 38 practice questions to prepare you well beyond it. (estimate)

38questions here

8free pages

13concepts

Questions 36–38

36foundation · easy
Which configuration option controls how often Prometheus evaluates alerting and recording rules?
Select an answer first
37expert · hard
A Prometheus server is configured to scrape a node_exporter on a remote host. The target appears as 'DOWN' in the Targets page. The engineer can curl the node_exporter endpoint from the Prometheus server and get valid metrics. What is the most likely cause of the target being DOWN?
Select an answer first
38expert · hard
A large organization has multiple independent Prometheus servers, each monitoring a separate data center. They want to create a central Prometheus that aggregates metrics from all these servers for a global view. They also want to ensure that if one data center's Prometheus is down, the central Prometheus still has the most recent data from the other data centers. Which approach is most appropriate?
Select an answer first

Finished these 3 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to DEVOPS-TOOLS-ENGINEER

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Professional Institute. “DEVOPS-TOOLS-ENGINEER” is a trademark of its owner, used for identification only.

704.2 Prometheus Monitoring (weight: 6) DEVOPS-TOOLS-ENGINEER Practice Questions (Page 8)

Questions 36–38

Which configuration option controls how often Prometheus evaluates alerting and recording rules?

A Prometheus server is configured to scrape a node_exporter on a remote host. The target appears as 'DOWN' in the Targets page. The engineer can curl the node_exporter endpoint from the Prometheus server and get valid metrics. What is the most likely cause of the target being DOWN?

Keep studying — 704 Security and Observability