diff --git a/testdata/client-side-operations-timeout/connection-churn.json b/testdata/client-side-operations-timeout/connection-churn.json
index 4a765ac070..55f74b73e2 100644
--- a/testdata/client-side-operations-timeout/connection-churn.json
+++ b/testdata/client-side-operations-timeout/connection-churn.json
@@ -5,8 +5,8 @@
     {
       "minServerVersion": "4.4",
       "topologies": [
-        "replicaset",
-        "sharded"
+        "standalone",
+        "replicaset"
       ]
     }
   ],
diff --git a/testdata/client-side-operations-timeout/connection-churn.yml b/testdata/client-side-operations-timeout/connection-churn.yml
index fa8f761654..f33d198bd5 100644
--- a/testdata/client-side-operations-timeout/connection-churn.yml
+++ b/testdata/client-side-operations-timeout/connection-churn.yml
@@ -4,7 +4,11 @@ schemaVersion: "1.9"
 
 runOnRequirements:
   - minServerVersion: "4.4"
-    topologies: ["replicaset", "sharded"]
+    # TODO(SERVER-96344): when using failpoints mongos returns MaxTimeMSExpired 
+    # after maxTimeMS, whereas mongod returns MaxTimeMSExpired after 
+    # max(blockTimeMS, maxTimeMS). Until this ticket is resolved, these tests 
+    # will not pass on sharded clusters.
+    topologies: ["standalone", "replicaset"]
 
 createEntities:
   - client: