Monitor and Understand Vault Telemetry VAULT-OPERATIONS-PROFESSIONAL Practice Questions (Page 2)

Questions 6–10

1. 6foundation · medium

   A Vault operator wants to set up alerting rules to detect when a Vault node is unable to keep up with incoming client requests. Which telemetry-based alerting rule best targets this operational issue?

   • AAlert when vault.core.handle_request returns a high value for the 'sum' attribute over a 5-minute window.
   • BAlert when vault.core.handle_request returns a high value for the 'count' attribute over a 5-minute window.
   • CAlert when the mean latency of vault.core.handle_request exceeds a threshold over a 5-minute window.
   • DAlert when the rate of vault.core.handle_request exceeds a threshold and the mean latency of vault.core.handle_request exceeds a corresponding threshold over a 5-minute window.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A Vault cluster is running in a Kubernetes environment. The operations team wants to configure Vault to emit telemetry to Prometheus. They have added the following configuration to the Vault config file: `telemetry { prometheus_retention_time = "24h" }`. However, they are not seeing any metrics in Prometheus. What is the most likely reason?

   • AThey need to configure the Prometheus server to scrape the Vault metrics endpoint at `/v1/sys/metrics`.
   • BThey need to set `statsd_address` to point to the Prometheus server.
   • CThey need to set `disable_hostname = true` to allow Prometheus to scrape the metrics.
   • DThey forgot to enable the Prometheus endpoint by setting `enable_prometheus_metrics = true`.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Which telemetry metric is used to monitor replication lag in a replicated Vault setup?

   • Avault.core.handle_request
   • Bvault.runtime.alloc_bytes
   • Cvault.replication.replication_last_wal
   • Dvault.core.unsealed
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A Vault cluster is configured with disaster recovery (DR) replication. The operations team is monitoring telemetry and notices that the `vault.replication.dr.wal_lag` metric is high. What is the primary concern with a high DR WAL lag?

   • AThe DR secondary is not receiving any data, indicating a replication failure.
   • BThe primary cluster is experiencing high write latency, affecting performance.
   • CThe DR secondary is experiencing high read latency, affecting performance.
   • DThe DR secondary may not have the latest data if the primary fails, leading to data loss.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A Vault cluster is configured with performance replication. The operations team is monitoring telemetry and notices that the `vault.replication.perf.wal_lag` metric is high, but the `vault.replication.perf.sync_progress` metric is also high. What does this combination indicate?

   • AThe primary is experiencing high write latency, causing the secondary to lag.
   • BThe secondary is actively syncing and making progress, but the lag is still high due to a large backlog.
   • CThe secondary is not syncing at all, and the high sync_progress is a false positive.
   • DThe replication is working normally, and these values are within the expected range.
   Reveal Solution Discussion Select an answer first