Linux Foundation Linux Foundation Prometheus- Certified-Associate PDF Linux Foundation Linux Foundation Prometheus- Certified-Associate PDF Questions Available Here at: https://www.certification-exam.com/en/dumps/linux-foundation-exam/prometheus- certified-associate-dumps/quiz.html Enrolling now you will get access to 224 questions in a unique set of Linux Foundation Prometheus-Certified-Associate Question 1 Which of the following is NOT a metric generated by Prometheus automatically when performing a scrape? Options: A. scrape_payload_bytes B. scrape_duration_seconds C. scrape_samples_scraped D. up Answer: A Explanation: INCORRECT: "up" is incorrect as this is a metric generated by Prometheus when it performs a scrape. INCORRECT: "scrape_duration_seconds" is incorrect as this is a metric generated by Prometheus when it performs a scrape. CORRECT: "scrape_payload_bytes" is the correct answer. INCORRECT: "scrape_samples_scraped" is incorrect as this is a metric generated by Prometheus when it performs a scrape. References: https://prometheus.io/docs/concepts/jobs_instances/#automatically-generated-labels-and-time-series Question 2 Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/ What is a Prometheus exporter? Options: A. A program that exposes metrics from a system that does not natively expose Prometheus metrics B. A code library that allows exposing Prometheus metrics C. A program that sends metrics to Prometheus D. An application directly instrumented with Prometheus metrics Answer: A Explanation: INCORRECT: "An application directly instrumented with Prometheus metrics" is incorrect as such an application would not require use of an exporter. INCORRECT: "A code library that allows exposing Prometheus metrics" is incorrect as this is the definition of a Prometheus client library. CORRECT: "A program that exposes metrics from a system that does not natively expose Prometheus metrics" is the correct answer. INCORRECT: "A program that sends metrics to Prometheus" is incorrect as applications do not send metrics directly to Prometheus. Some applications may push metrics to the Prometheus Pushgateway which Prometheus then scrapes, but that still is not an exporter. References: https://prometheus.io/docs/instrumenting/exporters/ Question 3 As a best practice, which of the following is a poor use of Alertmanager silencing? Options: A. Silence alerts from a set of servers which are undergoing routine maintenance B. Silence alerts from a server for brief period while it is being initialized C. Silence alerts from a server that is being deprovisioned D. Silence a specific alert for which notifications are no longer desired Answer: D Explanation: INCORRECT: "Silence alerts from a set of servers which are undergoing routine maintenance" is incorrect as this is an ideal use of Alertmanager silencing. CORRECT: "Silence a specific alert for which notifications are no longer desired" is the correct answer. Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/ If a particular alert is no longer desired on a permanent basis, the alerting rule should be adjusted or removed. INCORRECT: "Silence alerts from a server that is being deprovisioned" is incorrect as this is a good use of Alertmanager silencing. Many times Prometheus service discovery configurations will ensure that deprovisioned targets get dropped from monitoring and thus are not alerted on. Sometimes however, the alerting rule will evaluate before the target has been dropped and thus generate an unneeded alert. Silencing can help prevent this scenario. INCORRECT: "Silence alerts from a server for brief period while it is being initialized" is incorrect as this is a good use of Alertmanager silencing. Servers often can take a bit of time to fully initialize and run their exporters. If Prometheus discovers and scrapes the server during this time it could generate a false positive alert. Silencing can be a good way to prevent noise caused by this type of activity. Question 4 What is a Prometheus metrics registry? Options: A. A code library used for exposing Prometheus metrics B. A set of metrics in an instrumented application that will be returned when scraped C. A documentation site detailing the metrics provided by a specific exporter or instrumentation D. A documentation site detailing all of the public exporters and instrumentations Answer: B Explanation: INCORRECT: "A documentation site detailing the metrics provided by a specific exporter or instrumentation" is incorrect. Though many application and exporter maintainers will document the metrics exposed by the application, this documentation is not the metrics registry. A Prometheus metrics registry is a code concept within each Prometheus client library where metrics are registered to be returned when scraped. INCORRECT: "A documentation site detailing all of the public exporters and instrumentations" is incorrect. While the Prometheus documentation site does maintain a large list of available exporters, that is not what a metrics registry is. INCORRECT: "A code library used for exposing Prometheus metrics" is incorrect as this the definition of a Prometheus client library. CORRECT: "A set of metrics in an instrumented application that will be returned when scraped" is the correct answer. References: https://prometheus.io/docs/instrumenting/writing_clientlibs/#overall-structure Question 5 Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/ In an alerting rule, which syntax can be used to specify the value of a label called node within a different alert label or annotation? Options: A. {{ $labels.node }} B. label_value("node") C. $labels.node D. labels["node"] Answer: A Explanation: INCORRECT: "$labels.node" is incorrect as this expression must be surrounded by the Go templating curly braces ({{ and }}). INCORRECT: "labels["node"]" is incorrect CORRECT: "{{ $labels.node }}" is the correct answer. INCORRECT: "label_value("node")" is incorrect. References: https://prometheus.io/docs/prometheus/latest/configuration/template_examples/#simple-alert-field-templ ates Question 6 What is the purpose of Prometheus recording rules? Options: A. Evaluate a PromQL expression and save the result back to the TSDB as a new metric B. Record the screen of users of an application and generate metrics from their session C. Record the current state of all firing alerts for later analysis D. Define criteria for recording details of metrics for later retroactive evaluation of alerting rules Answer: A Explanation: INCORRECT: "Record the current state of all firing alerts for later analysis" is incorrect as recording rules are about recording the result of a PromQL metrics expression and do not deal with alerts. CORRECT: "Evaluate a PromQL expression and save the result back to the TSDB as a new metric" is the correct answer. INCORRECT: "Record the screen of users of an application and generate metrics from their session" is incorrect as this describes the process of Real User Monitoring. While useful for observability, this is not Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/ a feature of Prometheus or Alertmanager. INCORRECT: "Define criteria for recording details of metrics for later retroactive evaluation of alerting rules" is incorrect as alerting rules are not retroactively evaluated. References: https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/#recording-rules Question 7 What configuration is used to effectively disable grouping of alerts for a particular Alertmanager route? Options: A. group_by: ['*'] B. enable_grouping: false C. group_by: ['...'] D. disable_grouping: true Answer: C Explanation: INCORRECT: "disable_grouping: true" is incorrect as there is no such configuration option. Grouping is solely configured via the group_by attribute of a route. INCORRECT: "enable_grouping: false" is incorrect as there is no such configuration option. Grouping is solely configured via the group_by attribute of a route. INCORRECT: "group_by: ['*']" is incorrect as the actual syntax for grouping by everything (effectively disabling grouping) is .... CORRECT: "group_by: ['...']" is the correct answer. References: https://prometheus.io/docs/alerting/latest/configuration/#route Question 8 Which of the following is NOT a best practice when it comes to writing a Prometheus exporter? Options: A. Include a landing HTML page that links to the metrics path B. Include a version label on all exported metrics C. Drop statistical aggregations such as mean or median D. Follow the Prometheus best practices on metric naming Answer: B Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/ Explanation: INCORRECT: "Follow the Prometheus best practices on metric naming" is incorrect as this is a best practice. CORRECT: "Include a version label on all exported metrics" is the correct answer. This is not a best practice as it is recommend to use a designated build_info metric with a version label and dynamically attach it via PromQL grouping as-needed. INCORRECT: "Drop statistical aggregations such as mean or median" is incorrect as it is a best practice to not expose statistical aggregations as metrics and instead calculate them via PromQL. INCORRECT: "Include a landing HTML page that links to the metrics path" is incorrect as this is a best practice. References: https://prometheus.io/docs/instrumenting/writing_exporters/ [http://www.robustperception.io/how-to-have-labels-for-machine-roles/](http://www.robustperception.io/how- to-have-labels-for-machine-roles/) Question 9 How and at what level of granularity is Prometheus data retention configured? Options: A. Globally via the configuration file B. Per-scrape in command line flags C. Globally via command line flags D. Per-scrape in the configuration file Answer: C Explanation: INCORRECT: "Globally via the configuration file" is incorrect as retention is actually configured via the -- storage.tsdb.retention.time command line flag. CORRECT: "Globally via command line flags" is the correct answer. INCORRECT: "Per-scrape in the configuration file" is incorrect as retention is actually configured globally via the --storage.tsdb.retention.time command line flag. INCORRECT: "Per-scrape in command line flags" is incorrect as retention can only be configured globally, not on a per-scrape basis. References: https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects Question 10 You have configured the Elastic Kubernetes Service on AWS and have deployed Node Exporter to each Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/ of the hosts and configured it to be managed by systemd. Which of the following service discovery methods should you use to configure a Prometheus scrape for Node Exporter? Options: A. kubernetes_sd_configs B. static_sd_configs C. file_sd_configs D. ec2_sd_configs Answer: D Explanation: INCORRECT: "kubernetes_sd_configs" is incorrect. Since Node Exporter is being managed by systemd and not by a Kubernetes DaemonSet, there will be no Node Exporter pods to discover and thus kubernetes_sd_configs will not be effective. INCORRECT: "file_sd_configs" is incorrect as ec2_sd_configs is a better, built-in choice for dynamically identifying AWS instances to scrape. INCORRECT: "static_sd_configs" is incorrect as Kubernetes nodes are dynamic. Sometimes nodes will be added and other times nodes will be removed. In each of these cases, static target configuration would have to be manually updated. Thus, leveraging the built-in ec2_sd_configs is a better option. CORRECT: "ec2_sd_configs" is the correct answer. References: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#ec2_sd_config Would you like to see more? Don't miss our Linux Foundation Prometheus-Certified-Associate PDF file at: https://www.certification-exam.com/en/pdf/linux-foundation-pdf/prometheus-certified- associate-pdf/ Linux Foundation Linux Foundation Prometheus-Certified-Associate PDF https://www.certification-exam.com/