Question 170
After metadata inspection, XML files need one parser and JSON files another. Which state expresses the conditional route?
- Step Functions Catch transition
- Lambda timeout setting
- Step Functions execution input/output paths
- Step Functions Choice state
- Step Functions Map state
Explanation
Correct Answer
D:A Choice state routes execution based on a condition in the state input; in this scenario, evaluate the detected format and dispatch to the matching branch without creating an external polling controller.
Incorrect Answers
A:Catch handlers move execution to a recovery state when a configured task error occurs; it would target sending failed processing to a quarantine path, while the question is about selecting a branch after checking data type.
B:A Lambda timeout caps the maximum duration of a single function invocation; its benefit is preventing a stalled serverless task from running indefinitely; that is different from selecting a branch after checking data type.
C:InputPath, ResultPath and OutputPath can shape data passed between workflow states; the current need is for selecting a branch after checking data type, not retaining only relevant fields between processing tasks.
E:A Map state processes collection items using controlled parallel iterations in a workflow; this helps with applying the same transform to many independent input files, not selecting a branch after checking data type.
Question 171
An audit lake stores many months of structured access logs in S3 and analysts need cross-account SQL joins. Which approach fits?
- CloudWatch metric filter
- OpenSearch indexed log search
- Athena over structured S3 logs
- CloudWatch subscription filter
- CloudWatch Logs Insights
Explanation
Correct Answer
C:Athena can query centrally stored S3 audit logs after their schema is represented in a catalog; in this scenario, catalog the log structure and query it with Athena, partitioning by time or account to control scan cost.
Incorrect Answers
A:A metric filter creates CloudWatch metric datapoints from matching CloudWatch Logs events; the current need is for running SQL over accumulated S3 log archives, not alerting on a distinctive application error pattern.
B:OpenSearch can index log documents for search, filtering and operational dashboards; this can support searching high-cardinality text patterns across indexed application logs, but would not address the need for running SQL over accumulated S3 log archives.
D:Log subscription filters send matching events from CloudWatch Logs to supported downstream consumers; although useful for streaming selected application errors into a central processor, it leaves the need for running SQL over accumulated S3 log archives unmet.
E:Logs Insights searches and aggregates records in CloudWatch log groups with query syntax; it would target interactively grouping recent Lambda exception events from CloudWatch log groups, while the question is about running SQL over accumulated S3 log archives.
Question 172
Operations need Kinesis incoming throughput, Lambda iterator age and error rates visible together during incidents. Which observability feature fits?
- CloudWatch Logs retention policy
- CloudWatch dashboard
- CloudWatch metric anomaly detection
- CloudWatch custom metric
Explanation
Correct Answer
B:A dashboard displays chosen service and custom metrics in a shared operational view; in this scenario, build a dashboard with the related metrics and consistent time ranges to compare producer and consumer behavior.
Incorrect Answers
A:Log-group retention settings automatically remove old log events after an assigned retention period; this helps with controlling long-term storage of verbose ETL debug logs, not correlating stream lag with transformation failures.
C:Anomaly detection models a metric's historical range and alarms on unusual deviations; it would target catching unexpected deviations from a periodic pipeline pattern, while the question is about correlating stream lag with transformation failures.
D:Custom CloudWatch metrics record application-specific measurements not emitted by a service automatically; its benefit is monitoring per-batch invalid record counts; that is different from correlating stream lag with transformation failures.
Question 173
A data pipeline occasionally receives throttling responses during bursts and currently fails immediately. What SDK behavior helps?
- ECS task role credential provider
- Boto3 paginator
- SDK client retry configuration
- API response pagination contract
Explanation
Correct Answer
C:AWS SDK retry settings manage retry attempts and backoff for supported retryable API failures; in this scenario, configure an appropriate standard or adaptive retry mode and bounded attempts, keeping writes idempotent when applicable.
Incorrect Answers
A:The AWS SDK credential provider chain can obtain short-lived task-role credentials from an Amazon ECS task identity without static keys; the current need is for handling transient AWS service throttling from ETL code, not authenticating a scheduled ECS data-container AWS SDK client without static keys.
B:Boto3 paginators iterate AWS API responses that return continuation tokens and limited pages; this can support retrieving every object across paginated AWS API responses, but would not address the need for handling transient AWS service throttling from ETL code.
D:API consumers must follow service pagination and page-size contracts to avoid missing records; although useful for implementing a complete read of a partner's paginated REST feed, it leaves the need for handling transient AWS service throttling from ETL code unmet.
Question 174
A versioned landing bucket still accumulates old versions after daily object overwrites even though current files expire later. What lifecycle action helps?
- S3 Lifecycle expiration
- S3 Lifecycle noncurrent expiration
- S3 Object Lock retention
- S3 Lifecycle abort multipart upload
Explanation
Correct Answer
B:Noncurrent version expiration removes older object versions in versioned buckets according to policy; in this scenario, configure noncurrent-version expiration while checking retention and delete-marker behavior to prevent uncontrolled version growth.
Incorrect Answers
A:Lifecycle expiration removes eligible objects automatically after conditions such as object age are met; this can support deleting obsolete unversioned objects after a retention interval, but would not address the need for cleaning up superseded object versions.
C:S3 Object Lock enforces supported retention controls that can prevent object deletion during required periods; although useful for retaining evidence against premature deletion, it leaves the need for cleaning up superseded object versions unmet.
D:A lifecycle rule can remove incomplete multipart-upload parts after a configured age; it would target preventing orphaned upload parts from accumulating charges, while the question is about cleaning up superseded object versions.
Question 175
A daily batch contains repeated order_id values that would double-count sales if loaded as new facts. Which rule detects this?
- Non-null primary field check
- Uniqueness constraint test
- Cross-field consistency check
- Allowed-value domain check
Explanation
Correct Answer
B:Uniqueness checks detect duplicate keys within a dataset or business partition; in this scenario, check key uniqueness in the relevant scope and reconcile legitimate updates separately from accidental repeated events.
Incorrect Answers
A:Non-null validation checks reject or quarantine records missing mandatory business identifiers; its benefit is preventing records without required identifiers entering a curated table; that is different from identifying duplicate order IDs after source replay.
C:Cross-field validation evaluates relationships between columns rather than judging each field alone; this can support detecting logical contradictions in financial records, but would not address the need for identifying duplicate order IDs after source replay.
D:Domain checks ensure values belong to documented categories or ranges rather than arbitrary strings; this helps with rejecting unsupported transaction status codes, not identifying duplicate order IDs after source replay.
Question 176
The source account updated its CMK key policy but the reader role still lacks KMS Decrypt in its own effective permissions. What policy adjustment helps?
- TLS for JDBC connections
- Cross-account S3 bucket policy
- Client-side encryption before upload
- External role IAM KMS permission
- Cross-account KMS key policy
Explanation
Correct Answer
D:A consumer identity policy can permit use of an externally owned customer-managed KMS key when its key policy also allows it; in this scenario, add scoped KMS permissions on the designated key to the role, respecting resource policies and organization restrictions.
Incorrect Answers
A:TLS secures supported database client-server communications against interception in transit; this can support encrypting traffic from Glue to a relational database endpoint, but would not address the need for enabling a cross-account reader role to call KMS Decrypt.
B:An S3 resource policy can authorize an external principal to read particular object keys; this helps with allowing a partner role to reach shared encrypted object paths, not enabling a cross-account reader role to call KMS Decrypt.
C:Client-side encryption transforms plaintext into ciphertext before it leaves the originating application; although useful for ensuring raw plaintext never leaves the source environment, it leaves the need for enabling a cross-account reader role to call KMS Decrypt unmet.
E:A customer-managed KMS key policy can authorize a principal or external account for intended cryptographic operations; its benefit is granting a partner account permitted access to encrypted lake objects; that is different from enabling a cross-account reader role to call KMS Decrypt.
Question 177
A vector search system needs an approximate index with tunable numbers of candidate lists to probe. Which approach fits?
- Exact vector similarity scan
- IVF vector clustering
- HNSW approximate index
- Vector index recall tuning
Explanation
Correct Answer
B:IVF partitions vector space into coarse clusters and searches selected candidate lists during retrieval; in this scenario, iVF first narrows the vector candidates by centroid partitions; tune training and probes for recall versus latency.
Incorrect Answers
A:Exact similarity evaluates distances against all relevant embeddings rather than using approximate pruning; this helps with obtaining an exact ranking for a small embedding collection, not limiting searches to coarse vector clusters.
C:HNSW organizes vectors in a navigable proximity graph for approximate nearest-neighbor retrieval; it would target favoring search speed and recall in large vector indexes, while the question is about limiting searches to coarse vector clusters.
D:Recall measures how often approximate search finds neighbors present in an exact reference result set; its benefit is validating approximate-search quality against exact neighbors; that is different from limiting searches to coarse vector clusters.
Question 178
A Glue transformation has abundant worker capacity, but an input dataset is divided into only a handful of huge partitions and most executor slots remain idle. Which change should be evaluated?
- Glue job data partition tuning
- EMR managed scaling policies
- Glue job bookmark reset
- Glue job worker increase
- EMR step logs in S3
Explanation
Correct Answer
A:Spark partition sizing determines whether distributed ETL tasks can run evenly and make good use of available executor slots; in this scenario, increase appropriately balanced input or shuffle partition counts and check file sizes and task metrics so workers can run partitions concurrently.
Incorrect Answers
B:EMR managed scaling adjusts available node capacity under configured bounds for supported clusters; this can support matching variable Spark compute demand without constant oversizing, but would not address the need for raising parallel task utilization when a Glue read produces too few partitions.
C:Resetting a Glue bookmark permits an ETL job to reprocess previously tracked source data intentionally; this helps with replaying a corrected historical data batch, not raising parallel task utilization when a Glue read produces too few partitions.
D:More appropriate Glue worker resources can help when Spark tasks are genuinely CPU or memory constrained; although useful for reducing a resource-limited Glue job runtime, it leaves the need for raising parallel task utilization when a Glue read produces too few partitions unmet.
E:EMR cluster logging can preserve step and application output in an S3 log destination; it would target investigating a failed historical EMR processing step, while the question is about raising parallel task utilization when a Glue read produces too few partitions.
Question 179
A storage team needs records of access requests against an S3 landing bucket for a separate analysis process. What logging capability is relevant?
- CloudTrail event history
- Redshift system query logs
- DMS task logs
- S3 server access logging
Explanation
Correct Answer
D:S3 server access logs can record requests made to a bucket and deliver log files to a chosen destination; in this scenario, enable the supported bucket access-logging configuration and secure the destination, acknowledging delivery and completeness characteristics.
Incorrect Answers
A:CloudTrail event history exposes recent management activity for an account within its documented retention; this helps with tracing who changed a Glue job configuration recently, not reviewing bucket request activity in a storage-focused audit.
B:Redshift query and system logging views provide evidence about SQL execution and warehouse operations; although useful for tracing an unexpectedly expensive warehouse query, it leaves the need for reviewing bucket request activity in a storage-focused audit unmet.
C:DMS task logs record migration and change-capture operational events and diagnostic details; it would target diagnosing failed replication-table mappings, while the question is about reviewing bucket request activity in a storage-focused audit.
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.