問題文
Creating the external model fails with a credential mismatch. The team confirms the host and the path segments are spelled the same, but the endpoint address they were given carries a query string with the API version, and one path segment differs only in letter case. What is the root cause of the mismatch?
選択肢
- Query strings are allowed as long as they are URL encoded, and the whole address is compared without regard to letter case.
- Only the fully qualified domain name is compared, so neither the query string nor the casing of a path segment can affect the result.
- The mismatch comes from the database collation being case-sensitive, which is stricter than the specification requires, so switching the database to a case-insensitive collation resolves both details.
- The credential name must be a valid URL that carries no query string, and path segments other than the scheme and host are compared with a case-sensitive collation, so both details break the match.