Answer – D
Branch name has not been mentioned in the question for ProjectD. So the branch name will be default i.e. master.
In the yaml file, we will specify "- /data" folder under "exclude :" element under "paths:" element under default branch "master: " of the project "ProjectD"
A. A branch filter to exclude
Branch filter is applied when we have multiple branches under the same project. Hence this option is incorrect
B. A branch filter to include
Branch filter is applied when we have multiple branches under the same project. Hence this option is incorrect
C. A path filter to include
In the question, we have the requirement to exclude. Hence this is not correct.
D. A path filter to exclude
Yes, this is the correct solution.
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#ci-triggers
Answer – D
Branch name has not been mentioned in the question for ProjectD. So the branch name will be default i.e. master.
In the yaml file, we will specify "- /data" folder under "exclude :" element under "paths:" element under default branch "master: " of the project "ProjectD"
A. A branch filter to exclude
Branch filter is applied when we have multiple branches under the same project. Hence this option is incorrect
B. A branch filter to include
Branch filter is applied when we have multiple branches under the same project. Hence this option is incorrect
C. A path filter to include
In the question, we have the requirement to exclude. Hence this is not correct.
D. A path filter to exclude
Yes, this is the correct solution.
---------------------
When you specify paths, you must explicitly specify branches to trigger on. You can`t trigger a pipeline with only a path filter; you must also have a branch filter, and the changed files that match the path filter must be from a branch that matches the branch filter.
-------------------