Question 180
A research role may query transaction totals but must not read the customer email column in the same lake table. What control helps?
- Lake Formation LF-Tag permissions
- Lake Formation column permissions
- Lake Formation table SELECT
- Lake Formation data location permissions
Explanation
Correct Answer
B:Lake Formation supports fine-grained grants selecting only approved columns of governed tables; in this scenario, grant column-scoped SELECT access and verify all compatible data access routes enforce the intended policy.
Incorrect Answers
A:LF-Tags enable tag-based governance over supported catalog resources and scalable permission assignment; this can support granting access to datasets by business classification, but would not address the need for preventing access to sensitive columns without copying datasets.
C:Lake Formation grants can authorize SQL SELECT access on governed catalog tables for supported integrations; although useful for granting analysts read access to approved lake tables, it leaves the need for preventing access to sensitive columns without copying datasets unmet.
D:Data location permissions can authorize principals to create or alter governed catalog resources at registered storage locations; it would target allowing a controlled role to create tables in one registered S3 location, while the question is about preventing access to sensitive columns without copying datasets.
Question 181
A previously unknown vendor feed arrives and quality thresholds must be based on observed patterns rather than guesses. Which operation fits?
- DataBrew profile statistics
- Quality quarantine S3 prefix
- Glue Data Quality evaluation results
- DataBrew validation recipe
- Glue Data Quality ruleset
Explanation
Correct Answer
A:DataBrew profile jobs summarize null values, distributions and other properties of tabular input; in this scenario, generate a data profile and review completeness and distributions before committing to an enforceable ruleset.
Incorrect Answers
B:A separate S3 prefix can preserve rejected records for controlled remediation without polluting curated queries; this can support keeping invalid records available for debugging but out of production analytics, but would not address the need for measuring baseline data characteristics before quality rule design.
C:Quality evaluation results record which configured checks pass and fail for a tested dataset; this helps with tracking rule failures across successive daily runs, not measuring baseline data characteristics before quality rule design.
D:A DataBrew recipe records transformations that can normalize inconsistent values and produce an approved output; although useful for standardizing known fields before final quality evaluation, it leaves the need for measuring baseline data characteristics before quality rule design unmet.
E:Glue Data Quality supports rulesets for evaluating data quality against supported datasets and ETL flows; it would target applying repeatable quality checks in a Glue pipeline, while the question is about measuring baseline data characteristics before quality rule design.
Question 182
Analysts repeatedly run the same expensive sales aggregation on slowly changing Redshift tables. What can cache useful results?
- JDBC predicate pushdown
- Redshift materialized view refresh
- Spark broadcast join
- Incremental ETL merge
Explanation
Correct Answer
B:A materialized view stores precomputed query results that can be refreshed as base data changes; in this scenario, materialize the aggregate and choose a refresh strategy that meets data-freshness requirements without recomputing every dashboard load.
Incorrect Answers
A:Source-side predicates can reduce rows transferred from a JDBC database into a distributed ETL job; this can support filtering historical relational data before network transfer, but would not address the need for accelerating repeated joins and aggregations for warehouse users.
C:A broadcast join sends a small relation to worker nodes to avoid shuffling both sides of a join; although useful for reducing shuffle overhead when one lookup table is tiny, it leaves the need for accelerating repeated joins and aggregations for warehouse users unmet.
D:Incremental merges apply inserts and updates from new source changes instead of rebuilding the entire destination; it would target processing only changed business records after an initial load, while the question is about accelerating repeated joins and aggregations for warehouse users.
Question 183
Test and production have drifted because S3 notifications, queues and roles were configured manually. Which tool makes infrastructure repeatable?
- AWS CDK construct
- AWS SAM template
- CloudFormation change set
- AWS CloudFormation stack
Explanation
Correct Answer
D:CloudFormation provisions and updates AWS resources through declarative templates and stack change tracking; in this scenario, maintain the desired resources in versioned CloudFormation templates and apply controlled stack updates.
Incorrect Answers
A:AWS CDK expresses cloud infrastructure using supported programming languages that synthesize CloudFormation; its benefit is reusing programmable infrastructure definitions across teams; that is different from recreating the same data pipeline infrastructure in different accounts.
B:AWS SAM extends CloudFormation with serverless resource declarations for applications; the current need is for recreating the same data pipeline infrastructure in different accounts, not packaging Lambda and Step Functions assets as serverless infrastructure.
C:A change set previews proposed modifications to a stack before they are executed; this can support reviewing potentially destructive infrastructure updates, but would not address the need for recreating the same data pipeline infrastructure in different accounts.
Question 184
A pipeline role has GetObject allowed but still fails because an organization guardrail denies access outside approved Regions. What policy principle explains this?
- IAM policy condition key
- IAM permissions boundary
- IAM resource-scoped S3 policy
- IAM explicit deny precedence
Explanation
Correct Answer
D:An explicit deny in an applicable policy overrides otherwise allowing IAM statements; in this scenario, evaluate applicable SCP, identity and resource policy denies before adding broader permissions, because an explicit deny wins.
Incorrect Answers
A:IAM policy conditions can limit allowed API use based on supported request attributes and context; this helps with restricting object writes to approved encryption settings, not diagnosing access denied despite an Allow statement.
B:A permissions boundary limits the maximum effective permissions of a principal even when identity policies allow more; although useful for constraining delegated ETL-role administration, it leaves the need for diagnosing access denied despite an Allow statement unmet.
C:An IAM identity policy can scope supported S3 operations to specific bucket and object ARN patterns; it would target granting ETL read access to one landing prefix, while the question is about diagnosing access denied despite an Allow statement.
Question 185
Producers change an Avro event contract and downstream jobs fail because a required field disappears. What preventive mechanism helps?
- Controlled schema migration version
- Schema registry compatibility check
- Backward-compatible optional column
- Schema-on-read normalization
Explanation
Correct Answer
B:A schema registry can enforce defined compatibility rules for producers and consumers sharing encoded records; in this scenario, validate proposed schema versions against a configured compatibility policy before allowing producer rollout.
Incorrect Answers
A:Versioned schema migration scripts make database changes reproducible and reviewable across environments; it would target coordinating relational schema changes with ETL releases, while the question is about blocking incompatible event schema changes during deployment.
C:Adding an optional column can allow older records and consumers to coexist with newer schema versions; the current need is for blocking incompatible event schema changes during deployment, not introducing a nullable attribute without breaking old data.
D:Schema-on-read applies structure when data is queried or transformed rather than forcing one physical shape at ingestion; this can support retaining unpredictable third-party fields for later curation, but would not address the need for blocking incompatible event schema changes during deployment.
Question 186
Finance requires a monthly S3 snapshot of a reporting query already computed in Redshift. Which statement fits?
- Redshift staging table merge
- Redshift UNLOAD to S3
- Redshift COPY manifest
- Redshift COPY from S3
Explanation
Correct Answer
B:UNLOAD writes Redshift query results to S3 objects for exchange or downstream analysis; in this scenario, use UNLOAD with an S3 destination and selected output format, accounting for the role and object security settings.
Incorrect Answers
A:Loading into a staging table before a controlled merge separates ingestion from publication of target data; its benefit is atomically applying validated changes to warehouse tables; that is different from exporting a curated warehouse query result to the lake.
C:A COPY manifest specifies the exact objects that a load should consume for reproducibility; this can support preventing partial object sets during a warehouse load, but would not address the need for exporting a curated warehouse query result to the lake.
D:COPY loads supported data files from S3 into Redshift tables using managed parallel reads; this helps with ingesting a large staged dataset into warehouse tables, not exporting a curated warehouse query result to the lake.
Question 187
A growing DynamoDB table has uneven traffic across partition keys while total capacity is adequate. Which built-in behavior can help?
- DynamoDB adaptive capacity
- Client-side concurrency limit
- RDS Proxy connection pooling
- Kinesis on-demand capacity
- Exponential backoff with jitter
Explanation
Correct Answer
A:DynamoDB adaptive capacity can redistribute available throughput to heavily accessed partitions within service limits; in this scenario, adaptive capacity can allocate throughput where demand concentrates, but sustained hot-key design still merits attention.
Incorrect Answers
B:A semaphore or worker cap bounds simultaneous API requests sent by an ingestion job; the current need is for mitigating uneven partition access within a DynamoDB table, not keeping API requests below a known in-flight limit.
C:RDS Proxy pools application database connections and reduces connection churn against supported databases; this can support protecting a relational database from short-lived connection bursts, but would not address the need for mitigating uneven partition access within a DynamoDB table.
D:Kinesis on-demand mode adjusts stream capacity without manually planning shard counts for typical demand patterns; this helps with absorbing variable streaming ingestion demand without shard planning, not mitigating uneven partition access within a DynamoDB table.
E:Backoff and jitter distribute API retries in time after throttling responses or transient errors; although useful for preventing synchronized retries after a shared API quota is exhausted, it leaves the need for mitigating uneven partition access within a DynamoDB table unmet.
Question 188
Access requirements vary by whether catalog tables are labeled restricted, internal or public rather than by their physical bucket. Which approach fits?
- Cross-account bucket policy
- Lake Formation LF-Tag based access
- IAM ABAC with principal tags
- S3 access point policy
- IAM RBAC role assignment
- Session tag authorization
Explanation
Correct Answer
B:LF-Tag authorization grants governed table access based on metadata classifications and expressions; in this scenario, set and enforce LF-Tag permissions over governed datasets, ensuring tags cannot be modified by unauthorized principals.
Incorrect Answers
A:An S3 bucket resource policy can allow a designated external account or role to access selected objects; it would target authorizing direct read access from another AWS account, while the question is about authorizing lake assets by governed data classification.
C:Attribute-based access control compares principal and resource attributes through supported IAM condition keys; the current need is for authorizing lake assets by governed data classification, not mapping ETL roles to same-team tagged resources.
D:S3 access points offer distinct access controls and network policies for shared S3 datasets; this can support exposing one bucket to applications with different data-access boundaries, but would not address the need for authorizing lake assets by governed data classification.
E:Role-based access control groups permissions according to job functions or workload responsibilities; this helps with giving production operators a stable predefined permission set, not authorizing lake assets by governed data classification.
F:Session tags can carry approved attributes in assumed-role sessions for ABAC decisions; although useful for propagating per-session team attributes to authorization rules, it leaves the need for authorizing lake assets by governed data classification unmet.
Question 189
Query performance suffers because timestamps are scattered randomly across every Parquet row group. What layout change could help?
- Columnar encoding dictionary
- Sorting output by query predicates
- S3 object compaction
- Avoiding overpartitioned Spark output
Explanation
Correct Answer
B:Sorting records on frequently filtered fields can improve locality and block skipping for some engines; in this scenario, sort or cluster output by time before writing, then verify the engine uses statistics to skip irrelevant row groups.
Incorrect Answers
A:Dictionary encoding can efficiently represent repeated low-cardinality values in columnar storage formats; the current need is for increasing pruning efficiency inside large files, not compressing repeated categorical attributes efficiently.
C:Compaction combines many small analytic files into fewer appropriately sized objects; this helps with reducing excessive query task overhead, not increasing pruning efficiency inside large files.
D:Excessive Spark partitions can create scheduling overhead and tiny output objects on low-volume workloads; although useful for tuning parallel output granularity to data volume, it leaves the need for increasing pruning efficiency inside large files unmet.
Question 190
A new supplier sends literal 'unknown' in an amount field and the ETL cast now fails. Which correction is appropriate?
- Executor memory tuning
- Spark shuffle skew investigation
- Data type casting validation
- Glue error log inspection
Explanation
Correct Answer
C:Explicit type validation and casting prevent malformed input strings from corrupting typed transformations; in this scenario, validate or quarantine malformed values using a documented rule, rather than silently coercing every row to an arbitrary default.
Incorrect Answers
A:Spark executor memory and partition size affect whether large tasks spill or fail from memory pressure; its benefit is addressing executor out-of-memory errors on large partitions; that is different from handling unexpected nonnumeric values in a numeric column.
B:Spark stage metrics can reveal straggler tasks and imbalanced shuffle partitions in a join; the current need is for handling unexpected nonnumeric values in a numeric column, not finding a slow join caused by one hot key.
D:Glue job failures produce execution logs that distinguish syntax, credentials, schema and runtime failures; this helps with locating the precise failing operation in Glue, not handling unexpected nonnumeric values in a numeric column.