Question 140
Analysts need to detect repeated email values after normalization, and policy forbids recovering the original addresses from outputs. What approach might fit?
- Redshift dynamic data masking
- One-way hashing of identifiers
- Amazon Macie sensitive data discovery
- Data anonymization aggregation
- Deterministic PII tokenization
Explanation
Correct Answer
B:A cryptographic hash maps inputs to fixed outputs without keeping an ordinary reversible mapping; in this scenario, apply a suitable one-way, keyed or salted hashing design as required; consider low-entropy input guessing risks before relying on hashes alone.
Incorrect Answers
A:Masking policies can return altered column representations to database users based on defined privileges; its benefit is obscuring sensitive fields at query time for nonprivileged roles; that is different from comparing known identifiers without storing plaintext values.
C:Macie can examine supported S3 data for sensitive information and report discovery findings; this can support detecting unexpected sensitive content in S3 objects, but would not address the need for comparing known identifiers without storing plaintext values.
D:Aggregation can report measurements across groups while excluding direct person-level rows from published outputs; this helps with publishing population statistics without individual record detail, not comparing known identifiers without storing plaintext values.
E:Tokenization replaces sensitive identifiers with controlled surrogate values and protects the mapping separately; although useful for linking customer events without exposing raw identifiers, it leaves the need for comparing known identifiers without storing plaintext values unmet.
Question 141
An existing Windows-based extractor requires an ODBC DSN to read its reporting database. Which connector arrangement is appropriate?
- ODBC connector configuration
- Secrets-based JDBC authentication
- JDBC driver compatibility
- Glue VPC routing and DNS
Explanation
Correct Answer
A:ODBC connection settings rely on a driver and data-source configuration compatible with the application runtime; in this scenario, install the appropriate ODBC driver and configure its DSN and credentials in the extractor environment.
Incorrect Answers
B:ETL connections can retrieve database credentials from a secret rather than embedding plaintext; the current need is for integrating a tool that expects an ODBC data source, not separating sensitive credentials from ETL source code.
C:JDBC requires a driver compatible with the source database and its supported protocol; this can support making a Glue job connect to a vendor database, but would not address the need for integrating a tool that expects an ODBC data source.
D:Glue network connections need paths and DNS resolution to reach databases inside a VPC; this helps with resolving a JDBC timeout to an internal data source, not integrating a tool that expects an ODBC data source.
Question 142
A custom streaming consumer crashes during ingestion and must restart without silently skipping committed work. Which state should be persisted?
- Idempotent output writes
- Durable consumer checkpoints
- Managed Service for Apache Flink keyed windows
- Stateless transformation
- Kinesis retention adjustment
Explanation
Correct Answer
B:Checkpoints track a stream application's committed read position separately from the stream itself; in this scenario, commit the last safe stream offset or sequence position alongside durable processing semantics, then resume from that boundary.
Incorrect Answers
A:Idempotent writes make replaying the same logical input safe without duplicating downstream effects; it would target preventing duplicate target rows after event redelivery, while the question is about resuming from the last successfully processed record.
C:Managed Service for Apache Flink can maintain keyed window aggregates with checkpoint-based state recovery across streaming records; the current need is for resuming from the last successfully processed record, not running recoverable per-customer rolling-window totals in managed Flink.
D:Stateless processors derive each output solely from their current input and need no cross-event accumulated state; this can support applying independent per-record normalization rules, but would not address the need for resuming from the last successfully processed record.
E:Stream retention controls how long published records remain available for replay in Kinesis Data Streams; this helps with extending the recovery window for an offline consumer, not resuming from the last successfully processed record.
Question 143
Fifty analysts should share a consistent approved set of warehouse read privileges without individual grants on every table. What database object helps?
- Redshift GRANT on schema objects
- Redshift row-level security policy
- Redshift database role
- Redshift dynamic data masking
Explanation
Correct Answer
C:A Redshift database role groups database privileges that can be granted to multiple database users; in this scenario, define a role with the needed grants and assign membership, maintaining database permissions independently of IAM identity roles.
Incorrect Answers
A:Redshift SQL grants determine which database principals can access schemas, tables and other objects; its benefit is giving a reporting role SELECT on one curated table; that is different from administering common warehouse table permissions centrally.
B:Redshift row-level security can restrict table rows returned for principals under applied policies; the current need is for administering common warehouse table permissions centrally, not limiting warehouse query results to a user's assigned tenant.
D:Redshift dynamic data masking can change the presentation of sensitive columns according to database policy; this helps with hiding customer email values from ordinary warehouse readers, not administering common warehouse table permissions centrally.
Question 144
A DMS migration must read two finance tables but exclude other schemas held on the same database server. What should constrain source extraction?
- Glue JDBC partition predicates
- DMS table mapping rules
- Glue job bookmarks
- S3 prefix-based ingestion
Explanation
Correct Answer
B:DMS table mappings select source schemas and tables and can apply supported transformations; in this scenario, table selection rules restrict replicated objects; this is applied in the replication task rather than as downstream filtering.
Incorrect Answers
A:JDBC partitioning lets Glue spread relational reads over partitions instead of one serial scan; it would target accelerating a large batch read of a numeric-keyed table, while the question is about selecting only permitted source tables for replication.
C:Glue job bookmarks can track previously processed source data between supported job runs; the current need is for selecting only permitted source tables for replication, not avoiding the routine reread of already processed batches.
D:Explicit S3 prefixes narrow the object keys examined by a batch ETL input; this can support scoping a daily batch to the intended landing folder, but would not address the need for selecting only permitted source tables for replication.
Question 145
Two departments disagree about who may approve changes to a company-wide customer table. What organizational measure helps?
- SageMaker Catalog asset subscription approval
- Purpose-based data minimization
- Data governance stewardship roles
- Retention schedule governance
Explanation
Correct Answer
C:A governance framework assigns ownership and stewardship for datasets, definitions and access decisions; in this scenario, define a data owner and steward with documented approval and classification responsibilities before granting new access.
Incorrect Answers
A:SageMaker Unified Studio uses project-level data-asset subscription requests and approval workflows to grant governed Lake Formation table access; its benefit is approving a project subscription to a restricted catalog table; that is different from establishing accountability for shared business datasets.
B:Data minimization limits collected and shared fields to those needed for the approved use case; the current need is for establishing accountability for shared business datasets, not reducing unnecessary exposure in downstream analytics.
D:A retention schedule documents how long classes of data may be stored and when deletion or archiving is required; this helps with aligning lake cleanup with legal data retention obligations, not establishing accountability for shared business datasets.
Question 146
An S3 reader has object permissions but cannot read an SSE-KMS object due to a KMS access error. Which permission must be reviewed?
- KMS key policy permissions
- SSE-KMS on S3 objects
- RDS storage encryption
- EBS volume encryption
- S3 Bucket Key with SSE-KMS
Explanation
Correct Answer
A:Key policies define key-level permission foundations for KMS operations, alongside other applicable access policies; in this scenario, check key policy and any permitted IAM grants for Decrypt, including key state, Region and relevant encryption context.
Incorrect Answers
B:SSE-KMS uses an AWS KMS key for server-side encryption of objects stored in S3; this can support enforcing controlled key usage for stored sensitive lake objects, but would not address the need for allowing authorized ETL roles to decrypt with an existing customer-managed key.
C:RDS storage encryption uses KMS integration to protect underlying database storage and supported related backups; this helps with encrypting a managed relational source's stored data, not allowing authorized ETL roles to decrypt with an existing customer-managed key.
D:EBS encryption protects supported block volumes at rest and in transit between instance and volume; although useful for protecting EC2-attached processing scratch volumes, it leaves the need for allowing authorized ETL roles to decrypt with an existing customer-managed key unmet.
E:S3 Bucket Keys can reduce the number of KMS requests made for eligible SSE-KMS object operations; it would target reducing KMS request costs for many encrypted objects, while the question is about allowing authorized ETL roles to decrypt with an existing customer-managed key.
Question 147
Analysts cannot predict which old datasets will become popular, and manual tier rules keep misclassifying objects. What storage class helps?
- S3 Intelligent-Tiering
- S3 Standard-IA
- S3 Glacier Deep Archive
- S3 Glacier Flexible Retrieval
Explanation
Correct Answer
A:Intelligent-Tiering monitors eligible object access and can move objects between access tiers automatically; in this scenario, use automatic tier transitions for eligible data while accounting for monitoring and automation charges and minimum object-size behavior.
Incorrect Answers
B:Standard-IA provides lower storage pricing for infrequently accessed objects with retrieval charges and minimum-duration constraints; it would target storing infrequent but quickly retrievable lake archives, while the question is about handling unpredictable access frequency for retained objects.
C:Glacier Deep Archive targets very rarely accessed data with long retrieval expectations; its benefit is storing long-term archives at low storage cost; that is different from handling unpredictable access frequency for retained objects.
D:Glacier Flexible Retrieval offers archive storage with asynchronous retrieval options for infrequently needed objects; the current need is for handling unpredictable access frequency for retained objects, not archiving files when retrieval can take hours.
Question 148
One pipeline must react to Glue job failures but ignore successful completions. Which event mechanism supports precise matching?
- DynamoDB Streams Lambda trigger
- S3 Event Notifications
- Amazon EventBridge event pattern
- S3 EventBridge integration
Explanation
Correct Answer
C:EventBridge rules match event fields and route matching events to target services; in this scenario, match the Glue state-change event source and failed state using a rule, then route it to the alerting or recovery target.
Incorrect Answers
A:A Lambda event source mapping polls DynamoDB Streams and sends batches to the function; its benefit is processing database changes as they occur; that is different from routing only events that satisfy structured filters.
B:S3 event notifications publish supported object events to configured destinations such as SQS; the current need is for routing only events that satisfy structured filters, not notifying a worker when a new object lands.
D:S3 can send supported bucket events to EventBridge for routing across multiple targets; this helps with distributing new-object events through an event bus, not routing only events that satisfy structured filters.
Question 149
A data steward needs a simple SELECT and COUNT over a cataloged Parquet table, without Python or Spark notebooks. Which interface fits?
- Athena notebook Spark session
- Athena SQL editor
- Athena query-result S3 location
- Spark dataframe transformations
- Athena workgroup controls
Explanation
Correct Answer
B:Athena SQL editor runs interactive SQL queries over configured catalogs and workgroups; in this scenario, run the SQL from the Athena editor with the correct workgroup and query-result S3 permissions.
Incorrect Answers
A:Athena notebooks can provide an interactive Apache Spark environment for data exploration; the current need is for running ad-hoc SQL against Glue catalog tables, not exploring large datasets with Spark in an Athena-integrated notebook.
C:Athena SQL query results are written to an S3 output location subject to workgroup and permission settings; this helps with troubleshooting a query that fails before returning rows, not running ad-hoc SQL against Glue catalog tables.
D:Spark DataFrames provide distributed operations such as filters, joins and aggregations within supported notebook sessions; although useful for exploring joins on a distributed lake dataset, it leaves the need for running ad-hoc SQL against Glue catalog tables unmet.
E:Athena workgroups provide query settings, usage controls and separation for groups of users; it would target limiting scanned query cost for exploratory users, while the question is about running ad-hoc SQL against Glue catalog tables.
Question 150
An application deletes a key in a versioned S3 bucket, but earlier data versions remain stored. Which recovery operation fits?
- DynamoDB point-in-time recovery
- DynamoDB TTL attribute
- S3 bucket versioning
- S3 delete-marker recovery
- S3 MFA Delete
Explanation
Correct Answer
D:Deleting the current delete marker can reveal an older object version in a versioned bucket; in this scenario, locate and remove the current delete marker where appropriate, exposing the preserved prior object as current again.
Incorrect Answers
A:PITR supports continuous backups of a DynamoDB table within its supported recovery window; this helps with restoring a table after accidental bulk writes, not restoring a logically deleted current object.
B:DynamoDB TTL uses a specified numeric epoch-seconds attribute to expire items asynchronously; although useful for removing stale session records from DynamoDB, it leaves the need for restoring a logically deleted current object unmet.
C:Versioning preserves separate revisions of an object key to aid recovery from overwrites and deletes; it would target recovering a previously overwritten object revision, while the question is about restoring a logically deleted current object.
E:MFA Delete adds an MFA requirement to certain versioning-related delete operations when configured by the root account; the current need is for restoring a logically deleted current object, not adding strong protection to permanent deletion of object versions.