Metadata driven config in 3.4 with multiple filters applying to a given SP

[Michael A Grady]

When using metadata driven config in 3.4, what would happen if there are conflicting settings for a given SP? Not sure how likely it would be to happen "in the real world", but let's say you had a filter targeting all SPs with a given entity attribute tag, and a different filter doing something similar, or perhaps a RegEx. And a given SP falls into both, but one filter says use one context or nameid precedence, and the other specifies something different. (Or one says "sign assertions and not responses", and the other the opposite.) Does the first filter applied "win"? Or the "last filter applied"? Or would it be some unpredictable "mishmash" of the settings? 

--
Michael A. Grady
IAM Architect, Unicon, Inc.