TL;DR blogs and videos are for the impatient. Books focus on mastery. Mastering Ansible means setting up a local lab for testing full repeatable automation so you can confidential push out changes continously. That is why the book "Ansible for Devops" covers local lab setup with vagrant.
To the specific question is their a simplier book? Why would there be as blogs and videos will cover the "5 minute guide". Blogs or videos take hours or days of effort but books take months or years. The famous "for dummies" series breaks the mold but most technology books are going to be about mastery. As an "IT veteran" I had until recently overlooked how important videos are in learning new IT. Book publishers are having to adapt to the streaming generation and introductory books are going the way of the dodo.
The rest of this answer says why Ansible for Devops has early chapters on setting up a vagrant lab locally for testing.
Ansible is an agentless tool that runs commands in parallel over ssh. That's very different from many other tools that have a client-server-agent model where you have to install an agent on every server you deploy onto. This means that as long as your IaaS has ssh access, and they all do, you can run Ansible.
What is unique to every IaaS is how the networking is done or how hosts are created. Ansible starts after that assuming you have networking to your hosts and ssh access to those hosts. The Ansible for Devops book doesn't and shouldnt have a section on how to setup a test env on every IaaS provider. It focuses on setting up a test env on your local laptop. Not because that teaches about IaaS it's a load of new skills you need to make your laptop "an IaaS provider". It is because without that it's unlikely readers of the book are going to be able to master Ansible. Would you want to try to master a programming language that doesn’t run on your laptop?
If you work on physical or virtual machines with Ansible at a bank they might not let you run vagrant or Docker locally or even have admin rights to your laptop or root access on VMs. Mastering Ansible in those situations is really hard. You only have a few test boxes and you have to run the playbooks hundred of times on them to debug. How can you be sure your finished playbook will work first time on production boxes that you cannot access until go-live weekend when it must all work first time? You cannot. Why? Because your last test run on you test hosts might only have worked because of some setting you changes on those hosts weeks ago that you forgot to put into the playbooks.
People might ask "what's that to do with me as I don't have those issues”. The point is that if you can run vagrant on your laptop and you can rapidly test and experiment you can learn faster. You can also delete it all, and set it up from scratch, as final testing of your playbooks. That doesn't mean it will work first time on your IaaS if your ssh access to hosts and networking isn't set up but once they are you will be flying.
Mastering anything in the devops space isn't about "I finally got it working" its about "I can automate this to work first time in live and I can constantly improve it". That is why no book called "Ansible for Devops" would be worth buying if it didn't show you how to locally test against a multi server laboratory on your laptop.
I strongly recommend that people invest their time in setting up a lab on their laptop. It will save you weeks or months over a relatively short time frame. It's really annoying when your laptop has several different labs setup that get slightly conflicting software versions you have to debug but those few hours of extreme frustration pay back fast.