remove arbitrary querying

Author: XVincentX

graph/patterns/alternate-key.md

@@ -29,12 +29,7 @@ https://graph.microsoft.com/v1.0/users(email='[email protected]') Retrieves the em
 
 ---
 
-This pattern works and makes sense when the alternate key is good enough to identify a single resource and provides an useful alternative to the client; while it does not work if the resultset has more than one element.
-
-In such case, the workload has two choices:
-
-1. If the workload defines a list of alternate keys for a resource and the requested key is not there, the workload SHOULD return `422`
-2. If the workload does not have a list of alternate keys, it can still query the data source, but if the result yields more than a record, it SHOULD return `422` and encourage the user to use `$filter` rather than returning the first result of the query
+This pattern works and makes sense when the alternate key is good enough to identify a single resource and provides an useful alternative to the client; while it does not work if the resultset has more than one element. In such case, the workload SHOULD return `400`
 
 ## Example