I'd like to provide tips for others in bullet form:
Few of the questions were one-liners, maybe three out of the 65. Nearly all were wordy scenario-bases questions with wordy answers to read through. If you get one-liners, you're lucky. :)
When you take practice tests, prefer wordy ones that will take your timer down to the wire. I had 10-15 minutes left on my exam.
AWS Services with major emphasis: Elastic Beanstalk, CodeBuild, CodeDeploy, DynamoDB, s3, ElastiCache, ECS, RDS, AWS API, SNS, SQS. Know these inside and out and, better yet, how to combine them. Again, think scenarios. For example, CodeDeploy to update ECS; or how to get human approvals with CodePipeline. You'll also want to know the components of SQS messages.
They're really looking for developer-like thinking, so you won't get too many simple questions like "What is the maximum message size for SQS?" LoL More like, performance, migrating from on-prem to a AWS equivalents and how you might re-factor your app, and things not working questions... and then you have think about it as you mull the answers.
Don't fret though. Use process of elimination. That can help, but read carefully the answers, then re-read them before eliminating them. They can be sneaky.
Also, sometimes two answers are equally correct but you can only choose one. What to do! Well if you get those -- as I did where the solution could be either RDS or DynamoDB -- prefer the serverless option first! Next, the more secure option. Next, the cheapest or easiset option (i.e. fewest services).
Learn how to read a SAML XML document. A question came up on that and what it (the document) entitled the requesting app. SAML docs aren't huge and if you dissect one or two to learn the fields, you'll be fine. I didn't do that and I had to do it on the fly. (._.)
You can do this, just think scenarios (not one-line questions). I hope this help a little bit and good luck to the reader.