Question 260
A small Glue job finishes in minutes but consistently reserves many idle workers. What cost optimization should be evaluated?
- Column projection before scan
- Partition pruning
- EMR managed scaling
- Glue worker sizing and job profiling
Explanation
Correct Answer
D:Glue worker types and counts affect job parallelism, memory and billed compute consumption; in this scenario, inspect run metrics, reduce worker allocation where performance allows, and measure duration and DPU consumption together.
Incorrect Answers
A:Reading only required fields can reduce bytes processed by columnar storage and SQL queries; the current need is for right-sizing an oversized Glue ETL run, not minimizing scanned data during analytic transformations.
B:Partition pruning excludes dataset partitions whose values cannot satisfy a query predicate; this can support avoiding reads of unrelated months in a data lake, but would not address the need for right-sizing an oversized Glue ETL run.
C:EMR managed scaling can adjust cluster capacity within configured limits based on workload demand; this helps with reducing idle cluster capacity between Spark stages, not right-sizing an oversized Glue ETL run.
Question 261
A Spark workflow must adapt to controlled catalog changes without embedding S3 dataset schemas in source code. Which method helps?
- Catalog permissions boundary
- AWS Glue Data Catalog
- Apache Hive metastore
- Catalog API lookup
Explanation
Correct Answer
D:A data-processing application can query catalog APIs to discover schemas and data locations at runtime; in this scenario, retrieve the table definition using catalog APIs before reading, then validate expected compatibility with the job.
Incorrect Answers
A:Access to technical metadata and access to stored objects may be separately controlled by IAM and Lake Formation; it would target diagnosing why a visible table cannot be read, while the question is about avoiding hard-coded column lists in a dynamic ETL client.
B:Glue Data Catalog is a managed technical metadata repository for datasets and ETL integration; its benefit is centralizing technical table and partition definitions; that is different from avoiding hard-coded column lists in a dynamic ETL client.
C:Hive metastore maintains table and partition metadata for compatible Hadoop ecosystem tools; the current need is for avoiding hard-coded column lists in a dynamic ETL client, not retaining a legacy Hive-compatible metadata system.
Question 262
An S3 dataset uses a predictable date prefix pattern, and maintaining millions of catalog partitions becomes onerous. What Athena feature helps?
- Glue crawler partition update
- MSCK REPAIR TABLE
- Partition pruning predicate
- Athena partition projection
- ALTER TABLE ADD PARTITION
Explanation
Correct Answer
D:Partition projection computes partition locations from table properties instead of storing every partition explicitly; in this scenario, configure projection rules and storage templates that match actual S3 paths; query predicates supply projected values.
Incorrect Answers
A:A Glue crawler can discover supported new partitions and maintain catalog metadata during a run; this can support keeping partition metadata synchronized after scheduled ingestion, but would not address the need for avoiding per-day catalog updates for predictable partitions.
B:Athena's MSCK REPAIR TABLE can discover compatible Hive-style S3 partitions and add missing catalog entries; this helps with registering newly created Hive-style partition folders, not avoiding per-day catalog updates for predictable partitions.
C:Query filters on partition columns allow compatible engines to avoid scanning unrelated object prefixes; although useful for reducing reads after partition registration, it leaves the need for avoiding per-day catalog updates for predictable partitions unmet.
E:Adding a partition explicitly registers specified partition values and their locations in the catalog; its benefit is registering a small known list of partitions precisely; that is different from avoiding per-day catalog updates for predictable partitions.
Question 263
After exhausting retry attempts, a data-validation task must write a rejected-file record rather than fail without context. Which state-machine feature handles this?
- Step Functions execution input/output paths
- Lambda timeout setting
- Step Functions Map state
- Step Functions Catch transition
- Step Functions Choice state
Explanation
Correct Answer
D:Catch handlers move execution to a recovery state when a configured task error occurs; in this scenario, define a Catch transition to a quarantine or notification step, retaining error detail for later review.
Incorrect Answers
A:InputPath, ResultPath and OutputPath can shape data passed between workflow states; this can support retaining only relevant fields between processing tasks, but would not address the need for sending failed processing to a quarantine path.
B:A Lambda timeout caps the maximum duration of a single function invocation; this helps with preventing a stalled serverless task from running indefinitely, not sending failed processing to a quarantine path.
C:A Map state processes collection items using controlled parallel iterations in a workflow; although useful for applying the same transform to many independent input files, it leaves the need for sending failed processing to a quarantine path unmet.
E:A Choice state routes execution based on a condition in the state input; its benefit is selecting a branch after checking data type; that is different from sending failed processing to a quarantine path.
Question 264
Incident response needs fast free-text lookup over indexed exception messages from many pipeline components. Which backend is suitable?
- CloudWatch subscription filter
- CloudWatch Logs Insights
- Athena over structured S3 logs
- CloudWatch metric filter
- OpenSearch indexed log search
Explanation
Correct Answer
E:OpenSearch can index log documents for search, filtering and operational dashboards; in this scenario, ingest and index relevant log fields in OpenSearch while managing index retention and access controls.
Incorrect Answers
A: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 searching high-cardinality text patterns across indexed application logs unmet.
B: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 searching high-cardinality text patterns across indexed application logs.
C:Athena can query centrally stored S3 audit logs after their schema is represented in a catalog; its benefit is running SQL over accumulated S3 log archives; that is different from searching high-cardinality text patterns across indexed application logs.
D:A metric filter creates CloudWatch metric datapoints from matching CloudWatch Logs events; the current need is for searching high-cardinality text patterns across indexed application logs, not alerting on a distinctive application error pattern.
Question 265
Ingestion traffic has predictable weekly cycles and fixed thresholds generate false alarms during normal peaks. What alerting method helps?
- CloudWatch custom metric
- CloudWatch Logs retention policy
- CloudWatch dashboard
- CloudWatch metric anomaly detection
Explanation
Correct Answer
D:Anomaly detection models a metric's historical range and alarms on unusual deviations; in this scenario, use anomaly bands calibrated to the metric's history while keeping explicit alarms for hard contractual limits.
Incorrect Answers
A: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 catching unexpected deviations from a periodic pipeline pattern.
B:Log-group retention settings automatically remove old log events after an assigned retention period; the current need is for catching unexpected deviations from a periodic pipeline pattern, not controlling long-term storage of verbose ETL debug logs.
C:A dashboard displays chosen service and custom metrics in a shared operational view; this can support correlating stream lag with transformation failures, but would not address the need for catching unexpected deviations from a periodic pipeline pattern.
Question 266
A scheduled ECS task runs Python code that calls the Glue API. The container image currently includes a long-lived IAM access key. Which credential approach should replace that key?
- ECS task role credential provider
- Boto3 paginator
- SDK client retry configuration
- API response pagination contract
Explanation
Correct Answer
A:The AWS SDK credential provider chain can obtain short-lived task-role credentials from an Amazon ECS task identity without static keys; in this scenario, associate the required least-privilege IAM task role with the ECS task definition and use the SDK default credential provider chain.
Incorrect Answers
B:Boto3 paginators iterate AWS API responses that return continuation tokens and limited pages; it would target retrieving every object across paginated AWS API responses, while the question is about authenticating a scheduled ECS data-container AWS SDK client without static keys.
C:AWS SDK retry settings manage retry attempts and backoff for supported retryable API failures; its benefit is handling transient AWS service throttling from ETL code; that is different from authenticating a scheduled ECS data-container AWS SDK client without static keys.
D:API consumers must follow service pagination and page-size contracts to avoid missing records; the current need is for authenticating a scheduled ECS data-container AWS SDK client without static keys, not implementing a complete read of a partner's paginated REST feed.
Question 267
Archived compliance files must remain undeletable for seven years despite routine cleanup jobs. Which protection is appropriate?
- S3 Lifecycle abort multipart upload
- S3 Lifecycle noncurrent expiration
- S3 Object Lock retention
- S3 Lifecycle expiration
Explanation
Correct Answer
C:S3 Object Lock enforces supported retention controls that can prevent object deletion during required periods; in this scenario, set Object Lock retention in a compatible mode and assess legal and governance requirements before enabling deletion controls.
Incorrect Answers
A: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 retaining evidence against premature deletion.
B:Noncurrent version expiration removes older object versions in versioned buckets according to policy; its benefit is cleaning up superseded object versions; that is different from retaining evidence against premature deletion.
D: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 retaining evidence against premature deletion.
Question 268
A new source begins emitting unknown payment_status codes that reporting logic cannot interpret. What rule helps?
- Uniqueness constraint test
- Allowed-value domain check
- Cross-field consistency check
- Non-null primary field check
Explanation
Correct Answer
B:Domain checks ensure values belong to documented categories or ranges rather than arbitrary strings; in this scenario, compare status values with the approved vocabulary and quarantine or map exceptions only under an explicit business policy.
Incorrect Answers
A:Uniqueness checks detect duplicate keys within a dataset or business partition; this helps with identifying duplicate order IDs after source replay, not rejecting unsupported transaction status codes.
C:Cross-field validation evaluates relationships between columns rather than judging each field alone; it would target detecting logical contradictions in financial records, while the question is about rejecting unsupported transaction status codes.
D: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 rejecting unsupported transaction status codes.
Question 269
A cross-account KMS grant is correct but the destination role receives S3 AccessDenied before decrypting an object. Which access layer is missing?
- External role IAM KMS permission
- Cross-account S3 bucket policy
- TLS for JDBC connections
- Client-side encryption before upload
- Cross-account KMS key policy
Explanation
Correct Answer
B:An S3 resource policy can authorize an external principal to read particular object keys; in this scenario, grant the designated external principal the needed S3 read operations on the shared prefix, with any required listing scope.
Incorrect Answers
A:A consumer identity policy can permit use of an externally owned customer-managed KMS key when its key policy also allows it; it would target enabling a cross-account reader role to call KMS Decrypt, while the question is about allowing a partner role to reach shared encrypted object paths.
C:TLS secures supported database client-server communications against interception in transit; the current need is for allowing a partner role to reach shared encrypted object paths, not encrypting traffic from Glue to a relational database endpoint.
D:Client-side encryption transforms plaintext into ciphertext before it leaves the originating application; this can support ensuring raw plaintext never leaves the source environment, but would not address the need for allowing a partner role to reach shared encrypted object paths.
E:A customer-managed KMS key policy can authorize a principal or external account for intended cryptographic operations; this helps with granting a partner account permitted access to encrypted lake objects, not allowing a partner role to reach shared encrypted object paths.
Question 270
A compliance check has only a few thousand embeddings and must find the mathematically closest items without approximation error. What search method fits?
- HNSW approximate index
- Vector index recall tuning
- IVF vector clustering
- Exact vector similarity scan
Explanation
Correct Answer
D:Exact similarity evaluates distances against all relevant embeddings rather than using approximate pruning; in this scenario, compute exact distances and rank results, trading more work per query for exact nearest-neighbor results.
Incorrect Answers
A:HNSW organizes vectors in a navigable proximity graph for approximate nearest-neighbor retrieval; its benefit is favoring search speed and recall in large vector indexes; that is different from obtaining an exact ranking for a small embedding collection.
B:Recall measures how often approximate search finds neighbors present in an exact reference result set; the current need is for obtaining an exact ranking for a small embedding collection, not validating approximate-search quality against exact neighbors.
C:IVF partitions vector space into coarse clusters and searches selected candidate lists during retrieval; this can support limiting searches to coarse vector clusters, but would not address the need for obtaining an exact ranking for a small embedding collection.