Difficulty: Easy
Correct Answer: seldom
Explanation:
Introduction:
Organizations sometimes provision read-only databases for reporting, compliance, or distribution. The assignment of such work to team members depends on risk, tooling, and required expertise. This question probes common practice regarding who is tasked with building read-only instances.
Given Data / Assumptions:
Concept / Approach:
Creating a read-only database often touches replication topologies, permissions, and auditing. Mistakes can expose sensitive data or degrade production performance. Therefore, such work is seldom assigned to beginners without guidance; it is more commonly handled by experienced professionals or by juniors under close supervision.
Step-by-Step Solution:
1) Identify risk: misconfigured replication or permissions can cause outages or data leaks.2) Map risk to skill: tasks with higher operational risk are less frequently assigned to beginners.3) Conclude that the frequency is best described as “seldom.”
Verification / Alternative check:
Standard operating procedures typically require reviews, change controls, and senior sign-offs for replication and security-related changes—indicating it is not a routine beginner task.
Why Other Options Are Wrong:
Common Pitfalls:
Assuming “read-only” implies low risk. Security, consistency, and replication lag still matter greatly.
Final Answer:
seldom
Discussion & Comments