56. Under what conditions is it impossible to deploy a k8s cluster? - Such conditions do not exist; - It is impossible to deploy a cluster on a single node; - A separate node for API is required for deployment; - All control plane components of the cluster must be deployed on separate physical servers; 57. Which of the following is a message broker? - Apache Kafka; - Postgres; - OracleMQ; - RabbitMQ; - Asterix; - ActiveMQ; - Artemis;

56. Under what conditions is it impossible to deploy a k8s cluster?

• It is incorrect to say that such conditions do not exist — there are limitations.
• A Kubernetes cluster can be deployed on a single node (for example, using Minikube or kind), so the statement "impossible on a single node" is incorrect.
• A separate node for the API is not required — control components can be deployed on one or multiple nodes, including a single node.
• It is not necessary for all control elements to be on separate physical servers — they can be on virtual machines or containers.

Thus, a cluster cannot be deployed if:

• There is no access to necessary resources (e.g., network, permissions).
• Nodes do not meet the minimum resource requirements.

57. Which of the following is a message broker?

• Apache Kafka — message broker.
• RabbitMQ — message broker.
• ActiveMQ — message broker.
• Artemis — message broker (Apache ActiveMQ Artemis).

Not message brokers:

• Postgres — this is a DBMS.
• OracleMQ — such a product does not exist, perhaps Oracle MQ was meant, but this is not a standard name.
• Asterix — not a message broker, perhaps referring to Apache AsterixDB, which is a database.

Summary: message brokers include Apache Kafka, RabbitMQ, ActiveMQ, and Artemis.