Ansible Serial Keyword for Quorum in Rolling Updates

• ✓ A.It can be set as a percentage of the total hosts.
• ✓ B.It causes the playbook to run on a subset of hosts at a time.
• ✓ C.It can be combined with max_fail_percentage to control failure thresholds.
• D.It guarantees that only one task runs across all hosts at any time.
• E.It applies globally to all plays in the playbook.

Why A: Option A is correct because the 'serial' keyword in Ansible can be specified as a percentage (e.g., 'serial: 50%'), which tells Ansible to run the play on that percentage of hosts in the batch at a time. This is useful for controlling the rollout pace across a dynamic inventory where the exact host count may vary.

• ✓ A.Define a 'max_fail_percentage' to abort the update if too many hosts fail.
• ✓ B.Use the 'serial' keyword to update a subset of hosts at a time.
• C.Use 'strategy: free' to allow hosts to run tasks independently.
• D.Use 'gather_facts: no' to speed up the playbook.
• E.Set 'any_errors_fatal: true' to stop the update on the first failure.

Why A: Option A is correct because 'max_fail_percentage' allows you to define a threshold of host failures (as a percentage of the batch size) that, when exceeded, causes Ansible to abort the entire rolling update. This prevents the update from continuing when too many hosts have failed, which could lead to an inconsistent or degraded state across the infrastructure. Option B is correct because the 'serial' keyword controls the number of hosts (or percentage) that Ansible updates in each batch, ensuring that only a subset of hosts is taken out of service at a time, which maintains overall service availability during the rolling update.

• A.Set ignore_errors: yes to ensure the playbook continues even if some hosts fail.
• ✓ B.Use the serial keyword to update hosts in batches.
• C.Use the default serial setting (all hosts) for simplicity.
• ✓ D.Set max_fail_percentage to limit the number of failed hosts before aborting.
• E.Run all hosts in parallel to minimize total update time.

Why B: Option B is correct because the `serial` keyword in Ansible controls how many hosts are updated at a time during a rolling update, allowing you to update hosts in batches to maintain service availability. This is a best practice for coordinating rolling updates as it prevents overwhelming the infrastructure and ensures that a subset of hosts remains operational while others are being updated.

• A.Set serial: 0 to update all hosts simultaneously.
• ✓ B.Set serial to 10% and max_fail_percentage to 25%.
• C.Set forks to 100 and max_fail_percentage to 50.
• D.Set serial to 1 to update one host at a time with max_fail_percentage: 0.

Why B: Option B is correct because setting `serial: 10%` updates hosts in batches of 10% of the inventory, which parallelizes the update across many hosts to minimize total time, while `max_fail_percentage: 25%` provides a safety net by aborting the play if more than 25% of the batch fails, preventing a cascade of failures from taking down the entire data center. This combination balances speed and safety for large-scale rolling updates within a maintenance window.