Question 324 of 1,730
Database SecuritymediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is GRANT SELECT ON db_name.* TO 'user'@'%'; because this command precisely restricts the user to read-only access on all tables within a specific database in Amazon Aurora MySQL. The ON db_name.* clause targets every table in that database, while SELECT limits the privilege to queries only, preventing any INSERT, UPDATE, DELETE, or DDL operations. On the AWS Certified Database Specialty DBS-C01 exam, this scenario tests your understanding of granular privilege management in Aurora MySQL, a common topic where candidates often confuse GRANT with CREATE USER or mistakenly think REVOKE can assign permissions. A frequent trap is selecting ALTER USER, which modifies account settings like password or resource limits, not privileges. For the exam, remember the pattern: GRANT [privilege] ON [database].[object] TO [user] — and when you need read-only access to an entire database, the wildcard * after the database name is your key. Memory tip: "SELECT * is for reading, GRANT SELECT ON db.* is for restricting."

DBS-C01 Database Security Practice Question

This DBS-C01 practice question tests your understanding of database security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company is using Amazon Aurora MySQL-Compatible Edition. The database administrator wants to restrict a specific user to only execute SELECT statements on a specific database. Which SQL command should the administrator use?

Question 1mediummultiple choice
Read the full NAT/PAT explanation →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

GRANT SELECT ON db_name.* TO 'user'@'%';

Option C is correct because GRANT SELECT ON db_name.* TO user grants SELECT on all tables in the database. Option A is wrong because REVOKE removes privileges. Option B is wrong because CREATE USER creates a user but does not grant privileges. Option D is wrong because ALTER USER modifies user attributes.

Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ALTER USER 'user'@'%' WITH GRANT OPTION;

    Why it's wrong here

    Alters user to allow granting privileges, but does not grant SELECT.

  • CREATE USER 'user'@'%' IDENTIFIED BY 'password';

    Why it's wrong here

    Creates user but does not grant SELECT.

  • REVOKE ALL PRIVILEGES ON db_name.* FROM 'user'@'%';

    Why it's wrong here

    This revokes privileges, does not grant SELECT.

  • GRANT SELECT ON db_name.* TO 'user'@'%';

    Why this is correct

    Grants SELECT on all tables in the database.

    Related concept

    Authentication checks who the user is.

Common exam traps

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Detailed technical explanation

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Key takeaway

Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related DBS-C01 questions on access control and AAA configuration.

Related practice questions

Related DBS-C01 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DBS-C01 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DBS-C01 question test?

Database Security — This question tests Database Security — Authentication checks who the user is..

What is the correct answer to this question?

The correct answer is: GRANT SELECT ON db_name.* TO 'user'@'%'; — Option C is correct because GRANT SELECT ON db_name.* TO user grants SELECT on all tables in the database. Option A is wrong because REVOKE removes privileges. Option B is wrong because CREATE USER creates a user but does not grant privileges. Option D is wrong because ALTER USER modifies user attributes.

What should I do if I get this DBS-C01 question wrong?

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related DBS-C01 questions on access control and AAA configuration.

What is the key concept behind this question?

Authentication checks who the user is.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More DBS-C01 practice questions

Last reviewed: Jun 20, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DBS-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DBS-C01 exam.