Jenkins pipelines in microservices commonly use Groovy to define individual service build and deployment steps. Groovy is a scripting language that allows concise and powerful pipeline definitions.

Build Pipelines provide a powerful visual representation of Jenkins job dependencies and interactions. It allows experts to view and manage complex build workflows with a clear graphical interface.

Configuring Jenkins Failover ensures seamless job execution in a high-availability setup. If one Jenkins instance fails, another instance takes over to maintain continuous operation.

Jenkins achieves high availability by employing load balancing techniques and distributing master nodes to ensure continuous service even in the face of node failures.

The REST API in Jenkins primarily uses JSON format for job definitions. This format is widely used for its simplicity and ease of parsing, making it suitable for automated job creation.

Implementing distributed builds in Jenkins is essential for addressing scalability issues in an enterprise setup. Distributing builds across multiple nodes helps handle increased workloads efficiently.

The best course of action is to uninstall the problematic plugin and find a stable alternative. Disabling may not be sufficient, as the plugin might still have an impact on the system.

Jenkins typically triggers a build after a commit using the "Polling SCM" method. It periodically checks the source control system for changes, and if a change is detected, it initiates a build.

In a cloud environment, an important consideration for disaster recovery is ensuring data isolation and redundancy. This helps safeguard against data loss and ensures availability even in the event of infrastructure failures.

Source code version control is a basic feature to set up in Jenkins for implementing CI/CD pipelines. It allows tracking changes, managing versions, and facilitating collaboration among team members.