Red Hat OpenShift Administration III: Scaling Kubernetes Deployments in the Enterprise (DO380) Quiz Questions and Answers
Answer :
Automatically scales pods based on CPU utilization or custom metrics
Explanation :
The Horizontal Pod Autoscaler automatically adjusts the number of pod replicas in a replication controller, deployment, or replica set based on the observed CPU utilization or other select metrics.
To transfer log data to external systems for centralized processing
Explanation :
The primary role of log forwarding in OpenShift is to send log data to external systems for centralized collection, analysis, and retention, thus enhancing system observability and troubleshooting.
Increasing buffer size and setting a reliable delivery mode for forwarders
Explanation :
By increasing buffer size and setting up a reliable delivery mode, Fluentd can handle transient network failures without losing logs because they are stored temporarily before being forwarded.
To exploit cloud computing cost benefits and scalability
Explanation :
Implementing log forwarding to cloud services allows organizations to leverage cloud scalability, cost-efficiency, and integration with other cloud-native monitoring and alerting services.
The Cluster Monitoring Operator in OpenShift enables configuration of threshold-based alerting mechanisms to automatically respond to detected issues, improving the cluster's reliability.
On-demand auto-scaled nodes with high CPU resources
Explanation :
High-performance computing tasks can benefit from auto-scaled nodes that can dynamically adjust to meet CPU-intensive demands as they arise, optimizing performance and cost-effectiveness.
With a processing capacity of 5000 entries per second, the server handles 18,000,000 entries in an hour. With a 10% overhead, it processes 18,000,000 - 1,800,000 = 16,200,000 entries.
The Node Exporter collects hardware and operating system metrics exposed by Prometheus to perform detailed resource utilization analysis and detect anomalies within the cluster nodes.
It minimizes downtime and ensures application availability
Explanation :
A rolling update replaces pods incrementally which ensures the application remains available and minimizes disruptions, unlike the recreate strategy which involves complete downtime.
Facilitates external HTTP and HTTPS access to cluster services
Explanation :
An Ingress controller in OpenShift manages HTTP and HTTPS traffic from outside the cluster, directing it to appropriate services using Ingress resources which specify routing rules.
