What functions are performed by Foundry builds concerning branches? Select two.

Foundry builds play a crucial role in managing the development process by interacting with branches in specific ways that enhance workflow and version control. One of the primary functions is resolving job inputs and outputs concerning both the build branch and fallback branches. This involves identifying the data and resources required for the build process, ensuring that the correct versions are utilized. By coordinating dependencies and settings within the context of the current build and its fallback options, Foundry enables smoother operations and minimizes disruptions that could arise from using outdated or inappropriate data.

The focus on resolving job inputs and outputs is key to maintaining data integrity and improving efficiency. This function ensures that developers and data engineers can work confidently with the most relevant and stable versions of their data, which is vital in a multi-branch environment where projects are frequently in flux.

Regarding the other functions, creating new branches for each build could produce excessive branching without purposeful organization, and merging changes involves more complex processes that require review and coordination between branches, rather than being an automated task performed by builds. Automatically deleting unused branches, while potentially useful for cleanup, does not fall under the principal functions of build operations. Thus, the emphasis on resolving dependencies aligns with the essential responsibilities of Foundry builds.