CCNA Data Governance And Security Questions

Oracle Data Redaction applies a policy to a column so that queries return transformed values, such as partial masking, full masking, or randomized output, without changing stored data. A policy can be scoped to the analyst role while exempting the marketing application schema, letting campaign sends read the actual address. This matches the requirement precisely without duplicating or encrypting the underlying column.

Role-Based Access Control grants permissions according to a user's job role, so access to files is determined by role membership rather than individual ownership or arbitrary attributes. This satisfies the requirement that users access only files relevant to their role.

Masking replaces sensitive values while preserving column types, formats and referential relationships, so the test subset keeps production structure. This satisfies the stem's dual constraint: realistic structure for testing plus privacy protection, unlike full data fabrication or simple row sampling.

A RACI chart maps each data domain to the roles that are Responsible, Accountable, Consulted, and Informed. This directly documents domain ownership, single-point accountability for quality, and delegation of stewardship duties across business units. It is the artifact that translates governance intent into named assignments, making it the correct first deliverable for the committee's request.

Automated data lineage and lifecycle tracking maps where each record resides across all distributed nodes and enforces its deletion, producing auditable evidence that erasure requests were fulfilled everywhere. GDPR Article 17 requires demonstrating deletion across the whole cluster, which lineage tracking uniquely provides.

Data minimization requires that personal data collected be adequate, relevant, and limited to what is necessary for the purposes for which it is processed. Collecting only necessary data directly aligns with this principle, reducing privacy risks and compliance exposure.

Data quality standards are a recognised Data Governance component because they define measurable accuracy, completeness and consistency rules, plus remediation ownership. They satisfy the stem by converting governance policy into enforceable, auditable thresholds applied across the organisation's data assets.

Restricted data is typically the highest classification level in many data classification policies. It includes highly sensitive information such as trade secrets, personally identifiable information (PII), or protected health information (PHI). Unauthorized disclosure could cause severe legal, financial, or reputational damage. Therefore, it requires the strictest access controls, encryption, and monitoring.

A Cloud HSM provides tamper-resistant hardware that stores and manages encryption keys, performing cryptographic operations inside the module so plaintext keys never leave it. Only applications authorised to use the key handle can decrypt data, satisfying the authorised-decryption constraint.

Storage limitation requires that personal data be kept only as long as necessary for the purposes for which it is processed. Implementing deletion or anonymization after the purpose is fulfilled directly complies with this principle. It ensures data is not retained beyond its useful life, reducing risk and meeting GDPR Article 5(1)(e).

Regular reviews ensure the principle of least privilege.

HIPAA, the Health Insurance Portability and Accountability Act, is the US regulation that sets standards for protecting protected health information held by covered entities and their business associates, making it the act that specifically governs healthcare-related data protection.

PII includes data elements such as names, Social Security numbers, and account identifiers that can single out an individual, so its unauthorized disclosure typically triggers state breach-notification statutes. Classifying these retail records as PII aligns the governance program with legal duties to notify affected persons, regulators, or credit bureaus within mandated timeframes after a confirmed breach.

This satisfies both policy requirements: the grant is scoped to the schemas relevant to the reporting issue, and the expiration automatically removes access when the task ends. It minimizes standing privileges and produces a clear audit record of who had access and for how long.

Row-level security evaluates a predicate at query time and can reference session variables, so each analyst automatically sees only rows matching their portfolio. This enforces the restriction inside the database, independent of the BI tool, and works on the single shared table without duplicating data or relying on application code to add filters.

A Data Steward owns governance within a single business domain, defining and enforcing data quality, security, and lifecycle policies for that domain's data assets. This domain-scoped accountability satisfies the stem's requirement precisely, unlike enterprise-wide roles such as the CDO or operational roles such as data engineers.

Row-Level Security applies a predicate (typically via a security policy and inline table-valued function) that filters rows by the user's identity, so each user sees only permitted rows such as Region = 'North'. Column-level security or views would not enforce this per-user row filtering.

A view projecting only the approved columns enforces column-level restriction at the database layer. Revoking direct table privileges prevents the analyst from bypassing the view by querying the base table. This is the standard least-privilege pattern for limiting column visibility without duplicating data.

Dynamic Data Masking applies masking rules at query execution, so the HR analytics team sees obfuscated values while the stored data remains unchanged on disk. This satisfies the stem's constraint of obscuring PII at the query level without altering underlying storage, unlike encryption or static masking, which modify data at rest.

TLS provides secure, encrypted communication channels.

WORM storage policies lock objects so they cannot be altered or deleted until the retention period expires, satisfying the seven-year immutability requirement. Object Lock in compliance mode enforces this even against privileged users, supporting regulatory audit.

LDAP/Active Directory Integration provides the centralised directory service the company requires, letting database administrators authenticate against one authoritative store rather than separate local accounts. It satisfies the stem's centralised identity management constraint by consolidating administrator credentials, group membership and authentication policy into a single directory that databases can query directly.

S3 Lifecycle expiration rules automatically delete objects once a defined retention period elapses, satisfying GDPR erasure without manual intervention. This directly enforces the Right to be Forgotten at the object level, unlike replication or versioning settings, which retain data.

Physical destruction renders platters unrecoverable, while cryptographic erasure destroys the key protecting encrypted data, making it permanently inaccessible. Both defeat forensic recovery, unlike overwriting or degaussing, satisfying the requirement for the most secure handling of sensitive drives.

Referential integrity constraints ensure foreign keys in fact and dimension tables always match a valid primary key, preventing orphaned records. This blocks inconsistent relationships entering the warehouse, directly satisfying the integrity control the question demands.

Analysing access logs reveals which accounts, IP addresses and queries touched the affected data, establishing breach scope and root cause. This forensic step is essential during PII incident response to determine exposure extent and guide containment.

Generalizing fields such as postal code and age into broader ranges, and suppressing rare combinations, ensures each record is indistinguishable from at least k-1 others. This reduces re-identification risk from quasi-identifier combinations while leaving counts and distributions usable for aggregate statistics, matching the policy's dual requirement for the published permit dataset.

Biometric data is a special category under GDPR and protected personal information under CCPA because it uniquely identifies a person through physical or behavioural characteristics. This satisfies the scenario's requirement to name a data category covered by privacy legislation.

VPC endpoints let workloads reach storage services over private addresses inside the VPC, bypassing the public internet entirely. This satisfies the securing-storage requirement by removing internet exposure, and endpoint policies can further restrict which buckets or resources are reachable.

This control directly enforces the jurisdiction-specific retention rule by scoping deletion to EU records past the 30-day threshold, and the audit log provides evidence of compliance. It leaves US records untouched for the seven-year tax retention period, satisfying both obligations with one deterministic mechanism.

A ROPA documents each processing activity with its purpose, legal basis, categories of data subjects and personal data, recipients, retention periods, and security measures. It is precisely the artifact an auditor examines to verify that lawful basis and retention are defined per purpose, making it the correct evidence for the bank's compliance demonstration.

A cryptographic hash acts as a content fingerprint: if even one byte changes, the hash differs. Recording the hash alongside the archived extract and re-verifying before and after load proves the loaded data is byte-identical to what was archived, providing the non-repudiation evidence regulators require. This is the standard integrity control for ETL provenance.

Classification is only actionable when applied to a known asset inventory with accountable owners. Cataloging assets and attaching labels creates the authoritative record that downstream controls, audits, and retention schedules reference, and it exposes unmanaged data stores that would otherwise be missed.

CCPA grants consumers the right to receive their personal information in a portable format. Automated export routines let the company fulfil individual access requests promptly and consistently, satisfying the data portability obligation without manual extraction errors.

Always Encrypted performs cryptographic operations client-side, so the database engine never sees plaintext or keys. Storing the column master key in Azure Key Vault keeps key material outside SQL Server, satisfying the requirement that keys be managed externally.

Database audit logging captures administrative and user actions such as logins, privilege changes, and DDL statements within the database engine itself, providing the granular, tamper-evident record needed to audit all administrative actions on the server.

Retention policies specify how long each data category is kept and when lawful disposal occurs, directly governing the lifecycle's storage and destruction phases. This satisfies the stem's requirement for good lifecycle management by preventing indefinite accumulation and aligning disposal with legal and business obligations.

Stewardship assigns named owners who resolve conflicts, approve changes, and monitor quality for each domain. Without clear accountability, duplicate or contradictory customer records persist because no one is empowered to arbitrate. This practice directly supports trustworthy golden records by making ownership and decision rights explicit across the business units that contribute data.

Column-level encryption with keys held externally means the DBA sees only ciphertext in the 'diagnosis' column, satisfying the mandate that administrators cannot read plaintext PHI. The application, which holds or retrieves the key, encrypts before insert and decrypts after select, so filtering can still occur on decrypted values or on deterministic tokens, preserving query functionality.

Row-level security policies automatically filter rows based on the tenant identifier associated with the user's session. This ensures that each customer can only access their own data, even though all data resides in the same tables. RLS is a standard technique for multi-tenant isolation in shared databases, enforcing logical separation without requiring separate schemas or databases.

PII is a primary driver of confidential classification because unauthorized disclosure can cause identity theft, regulatory penalties, and reputational harm. Classification policies typically place PII at the confidential or restricted tier, triggering encryption, access controls, and breach notification obligations under laws such as GLBA and state privacy statutes.

Maintaining the data catalog's metadata — definitions, owners, lineage, classifications — is a continuous governance duty. It satisfies the stem because stewardship of business glossaries and technical metadata keeps data discoverable and accountable, which is administrative work performed under governance policy.

Personally Identifiable Information uniquely identifies an individual, so its exposure triggers legal and regulatory duties that generic data lacks. This satisfies the stem's enhanced-protection constraint, since PII demands stricter controls such as encryption, access restrictions and audit trails under regimes like UK GDPR.

Digital signatures use a private key to sign data, and anyone with the public key can verify the signature. This provides non-repudiation because only the holder of the private key could have created the signature. It also ensures integrity and origin authentication, directly meeting the requirement.

Client-Side Field Level Encryption encrypts specified fields in the driver before they reach mongod, so even a compromised database credential or server cannot read plaintext tenant data. Scoping keys per tenant means one tenant's key material cannot decrypt another tenant's fields, directly addressing the cross-tenant exposure concern stated in the policy.

DAM sensors must know which tables and columns hold regulated data before they can monitor access meaningfully. Identifying sensitive data objects scopes the monitoring policy, so alerts and audit rules apply to the assets that actually matter rather than generating noise across the whole database estate.

Database Activity Monitoring inspects and logs all database transactions in real time, including privileged administrator activity, while the firewall component blocks suspicious sessions. Together they detect and prevent exfiltration attempts by a rogue administrator, who bypasses ordinary access controls.

A data stewardship program assigns clear accountability for data quality to data owners and stewards within each business domain. It establishes roles, responsibilities, and escalation procedures to resolve issues before they impact regulatory reporting. This directly addresses the need for formal accountability across multiple business units and ensures data quality is managed at the source.

An S3 bucket policy is a resource-based IAM policy attached directly to the bucket, letting you grant or deny access by principal, such as the Finance team's IAM role, at the bucket level. This satisfies the constraint of restricting the specific bucket to only Finance members.

Assigning explicit data ownership roles names accountable stewards for each dataset, so decisions on quality, access and usage have a responsible party. This satisfies the governance best-practise requirement by removing ambiguity over who answers for the data.

A Data Processing Agreement satisfies GDPR Article 28, which mandates a binding contract between controller and processor. It sets lawful processing instructions, security obligations, sub-processor rules and audit rights, establishing the legal basis the stem requires. Microsoft Entra ID is unrelated here; the DPA is the specific instrument demanded.

Defaulting privacy settings to the most restrictive level enforces data minimisation and purpose limitation at the design stage, requiring users to opt in to sharing. This satisfies Privacy by Design by making protection the baseline rather than an afterthought.

Default accounts with unchanged default passwords let anyone with published vendor credentials authenticate directly, bypassing every other control. This is the highest-risk finding because it grants immediate, unauthenticated access to the database, unlike misconfigurations that merely weaken defences.

Data disposition is the lifecycle phase in which data is securely destroyed or otherwise removed once it reaches the end of its retention period, satisfying legal, regulatory and business requirements. It follows archival and precedes any residual audit reporting.

Audit logs tied to unique user IDs bind each transaction to an authenticated identity, preventing a user from later denying having performed it. This attribution satisfies non-repudiation, which requires irrefutable proof of the transaction's origin and actor.

Classifying and inventorying data establishes what information exists, where it resides and its sensitivity, providing the foundation every subsequent policy, ownership and control decision depends on. Without this baseline, governance roles and protections cannot be scoped meaningfully.

A DPIA systematically identifies and mitigates high risks to data subjects' rights and freedoms arising from processing, satisfying GDPR Article 35's requirement before processing begins. It documents necessity, proportionality and safeguards, enabling the controller to evidence accountability to supervisory authorities.

Classification tags unstructured data by regulatory obligation and business sensitivity, which determines how long each category is kept and how it is destroyed. This satisfies the retention policy by giving retention schedules and disposal methods a defensible, risk-based foundation.

Row-Level Security enforces predicates at query time so each tenant's session only returns rows matching its tenant identifier, preventing cross-tenant reads within a shared table. This satisfies the isolation requirement without separate databases per tenant.

Warehouse access history records which objects were read, by which role or user, and when, which directly answers who touched the regulated dataset during the window. Correlating those entries with role grants shows whether each access was authorized, producing the precise evidence auditors request.

IDOR occurs when an application exposes internal object identifiers and fails to verify that the requesting user is entitled to that record, letting attackers access other users' data by altering the reference. It is a direct symptom of broken access control in database-backed applications.

Authentication mechanisms verify a claimed identity before any access decision is made, forming the first pillar of an IAM framework. Without this verification step, authorisation and accounting cannot function, so it directly satisfies the stem's requirement for an essential IAM component.

BYOK lets the organisation generate and manage its own key material in the cloud KMS, so the provider never holds the root key. This directly satisfies the control requirement, since key custody, rotation and revocation remain with the customer rather than the vendor.

A trigger firing on UPDATE captures the change at the database engine level, recording current_user and now() regardless of the connecting application. This produces an authoritative, tamper-evident trail tied to the database session, exactly what auditors need for attribution. It also captures changes made through ad hoc SQL, not just through the application.

Database DLP tools inspect and block access to sensitive records in real time, catching malicious or accidental exfiltration by authorised users whose legitimate credentials would otherwise bypass perimeter controls, directly addressing the insider threat scenario.

Triggers on the diagnosis table can insert the old value, new value, timestamp, and current user into a separate append-only audit table. Revoking UPDATE and DELETE privileges on that audit table from all application and administrative roles makes the history tamper-evident, which satisfies the auditor's requirement that changes be permanently recorded and not alterable by the originating user.

The Data Governance Charter establishes the framework's scope, principles and decision rights, explicitly assigning accountabilities such as Data Owner, Data Steward and Data Custodian. It is the governing document that defines who is responsible for which data assets.

A data steward is responsible for the operational management of data assets within a domain, including defining business rules, monitoring quality, and resolving issues. This role bridges business and IT and is the standard assignment for day-to-day data quality stewardship in governance frameworks.

Native auditing captures user identity, timestamp, and SQL text at the database layer. Forwarding logs to an append-only central system outside the database prevents privileged database users from tampering with the evidence. This combination satisfies both completeness and integrity requirements for an audit trail.

Resource policies prevent the creation of assets outside allowed regions.

Redacting sensitive fields at the source stops raw personal data entering logs at all, so only non-sensitive content persists. This enforces data minimisation by limiting collected data to what is necessary, rather than relying on downstream deletion or access controls.

Data cataloguing inventories data assets with metadata, lineage and classification, letting staff locate every record linked to an individual. That directly satisfies the stem's CCPA constraint: responding to Right to Know requests requires knowing which datasets hold personal data and where it flows.

Configuring the database authentication policy within the IAM layer enforces complexity rules directly at the database engine, satisfying the requirement for database-level enforcement rather than relying on operating system or Microsoft Entra ID controls. This ensures every credential created or rotated inside the database must meet the defined complexity criteria before acceptance.