Book Image

AWS Certified Database – Specialty (DBS-C01) Certification Guide

By : Kate Gawron
5 (1)
Book Image

AWS Certified Database – Specialty (DBS-C01) Certification Guide

5 (1)
By: Kate Gawron

Overview of this book

The AWS Certified Database – Specialty certification is one of the most challenging AWS certifications. It validates your comprehensive understanding of databases, including the concepts of design, migration, deployment, access, maintenance, automation, monitoring, security, and troubleshooting. With this guide, you'll understand how to use various AWS databases, such as Aurora Serverless and Global Database, and even services such as Redshift and Neptune. You’ll start with an introduction to the AWS databases, and then delve into workload-specific database design. As you advance through the chapters, you'll learn about migrating and deploying the databases, along with database security techniques such as encryption, auditing, and access controls. This AWS book will also cover monitoring, troubleshooting, and disaster recovery techniques, before testing all the knowledge you've gained throughout the book with the help of mock tests. By the end of this book, you'll have covered everything you need to pass the DBS-C01 AWS certification exam and have a handy, on-the-job desk reference guide.
Table of Contents (24 chapters)
1
Part 1: Introduction to Databases on AWS
Free Chapter
2
Chapter 1: AWS Certified Database – Specialty Overview
5
Part 2: Workload-Specific Database Design
12
Part 3: Deployment and Migration and Database Security
16
Part 4: Monitoring and Optimization
20
Part 5: Assessment
21
Chapter 16: Exam Practice

Overview of Amazon QLDB

Amazon QLDB is a fully managed, transparent, immutable, and cryptographically verifiable transaction log database. What does this really mean? If you consider running an UPDATE or DELETE statement against a typical RDBMS, what happens? If you have logging enabled, then that transaction should be stored in the logs, but there will be no record of the change within the database. It would be fairly simple for someone to make changes and for those logs to be deleted or lost (how long are transaction logs kept for before being deleted?), and then all record of that change is also lost. QLDB not only stores the latest version of a record after it's been updated or deleted but also stores all the previous versions within the database itself. Additionally, the database ensures that every new version of a record contains an algorithmic reference to the previous version, meaning that any attempt to modify a record without making a record of the change will cause...