Question 360
A custom uploader frequently fails before CompleteMultipartUpload and leaves billed incomplete parts. What cleanup rule addresses this?
- S3 Lifecycle noncurrent expiration
- S3 Object Lock retention
- S3 Lifecycle expiration
- S3 Lifecycle abort multipart upload
Explanation
Correct Answer
D:A lifecycle rule can remove incomplete multipart-upload parts after a configured age; in this scenario, abort incomplete multipart uploads after a safe interval; this does not remove fully completed objects.
Incorrect Answers
A:Noncurrent version expiration removes older object versions in versioned buckets according to policy; this can support cleaning up superseded object versions, but would not address the need for preventing orphaned upload parts from accumulating charges.
B:S3 Object Lock enforces supported retention controls that can prevent object deletion during required periods; this helps with retaining evidence against premature deletion, not preventing orphaned upload parts from accumulating charges.
C:Lifecycle expiration removes eligible objects automatically after conditions such as object age are met; although useful for deleting obsolete unversioned objects after a retention interval, it leaves the need for preventing orphaned upload parts from accumulating charges unmet.
Question 361
A refund feed sometimes records refund_amount greater than original_payment_amount even when both values are numeric. What rule is needed?
- Allowed-value domain check
- Uniqueness constraint test
- Cross-field consistency check
- Non-null primary field check
Explanation
Correct Answer
C:Cross-field validation evaluates relationships between columns rather than judging each field alone; in this scenario, validate the conditional relationship between measures and route contradictions for investigation before they affect aggregates.
Incorrect Answers
A:Domain checks ensure values belong to documented categories or ranges rather than arbitrary strings; its benefit is rejecting unsupported transaction status codes; that is different from detecting logical contradictions in financial records.
B:Uniqueness checks detect duplicate keys within a dataset or business partition; the current need is for detecting logical contradictions in financial records, not identifying duplicate order IDs after source replay.
D:Non-null validation checks reject or quarantine records missing mandatory business identifiers; this helps with preventing records without required identifiers entering a curated table, not detecting logical contradictions in financial records.
Question 362
A compliance review discovers a JDBC client is configured for plaintext connections to its source database. What should be required?
- Client-side encryption before upload
- External role IAM KMS permission
- TLS for JDBC connections
- Cross-account S3 bucket policy
- Cross-account KMS key policy
Explanation
Correct Answer
C:TLS secures supported database client-server communications against interception in transit; in this scenario, enable and validate TLS on the JDBC path using trusted server certificates and supported connection settings.
Incorrect Answers
A: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 encrypting traffic from Glue to a relational database endpoint.
B:A consumer identity policy can permit use of an externally owned customer-managed KMS key when its key policy also allows it; this helps with enabling a cross-account reader role to call KMS Decrypt, not encrypting traffic from Glue to a relational database endpoint.
D:An S3 resource policy can authorize an external principal to read particular object keys; it would target allowing a partner role to reach shared encrypted object paths, while the question is about encrypting traffic from Glue to a relational database endpoint.
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 encrypting traffic from Glue to a relational database endpoint.
Question 363
A new index is very fast but misses several known relevant documents in similarity tests. Which evaluation action is appropriate?
- HNSW approximate index
- IVF vector clustering
- Exact vector similarity scan
- Vector index recall tuning
Explanation
Correct Answer
D:Recall measures how often approximate search finds neighbors present in an exact reference result set; in this scenario, compare approximate candidates with a ground-truth exact search and tune index search depth to improve recall.
Incorrect Answers
A:HNSW organizes vectors in a navigable proximity graph for approximate nearest-neighbor retrieval; this helps with favoring search speed and recall in large vector indexes, not validating approximate-search quality against exact neighbors.
B:IVF partitions vector space into coarse clusters and searches selected candidate lists during retrieval; although useful for limiting searches to coarse vector clusters, it leaves the need for validating approximate-search quality against exact neighbors unmet.
C:Exact similarity evaluates distances against all relevant embeddings rather than using approximate pruning; it would target obtaining an exact ranking for a small embedding collection, while the question is about validating approximate-search quality against exact neighbors.
Question 364
EMR jobs run slowly at peaks but the cluster remains costly and idle between stages. What capacity feature could help?
- Glue job worker increase
- Glue job bookmark reset
- Glue job data partition tuning
- EMR managed scaling policies
- EMR step logs in S3
Explanation
Correct Answer
D:EMR managed scaling adjusts available node capacity under configured bounds for supported clusters; in this scenario, set sensible managed scaling limits and validate application behavior during scale-down and executor replacement.
Incorrect Answers
A:More appropriate Glue worker resources can help when Spark tasks are genuinely CPU or memory constrained; the current need is for matching variable Spark compute demand without constant oversizing, not reducing a resource-limited Glue job runtime.
B:Resetting a Glue bookmark permits an ETL job to reprocess previously tracked source data intentionally; this can support replaying a corrected historical data batch, but would not address the need for matching variable Spark compute demand without constant oversizing.
C:Spark partition sizing determines whether distributed ETL tasks can run evenly and make good use of available executor slots; this helps with raising parallel task utilization when a Glue read produces too few partitions, not matching variable Spark compute demand without constant oversizing.
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 matching variable Spark compute demand without constant oversizing.
Question 365
A DMS replication task stops on one source table during CDC while other tables remain healthy. Which logs help isolate the failure?
- S3 server access logging
- CloudTrail event history
- DMS task logs
- Redshift system query logs
Explanation
Correct Answer
C:DMS task logs record migration and change-capture operational events and diagnostic details; in this scenario, examine the task's diagnostic log stream and table statistics for mapping, schema or source-log errors.
Incorrect Answers
A:S3 server access logs can record requests made to a bucket and deliver log files to a chosen destination; this helps with reviewing bucket request activity in a storage-focused audit, not diagnosing failed replication-table mappings.
B:CloudTrail event history exposes recent management activity for an account within its documented retention; although useful for tracing who changed a Glue job configuration recently, it leaves the need for diagnosing failed replication-table mappings unmet.
D:Redshift query and system logging views provide evidence about SQL execution and warehouse operations; its benefit is tracing an unexpectedly expensive warehouse query; that is different from diagnosing failed replication-table mappings.
Question 366
A curator can use existing governed tables but cannot register a new table under an approved location. Which Lake Formation control should be reviewed?
- Lake Formation table SELECT
- Lake Formation LF-Tag permissions
- Lake Formation data location permissions
- Lake Formation column permissions
Explanation
Correct Answer
C:Data location permissions can authorize principals to create or alter governed catalog resources at registered storage locations; in this scenario, check registered location permissions and the principal's ability to create catalog tables at the approved path.
Incorrect Answers
A:Lake Formation grants can authorize SQL SELECT access on governed catalog tables for supported integrations; this can support granting analysts read access to approved lake tables, but would not address the need for allowing a controlled role to create tables in one registered S3 location.
B:LF-Tags enable tag-based governance over supported catalog resources and scalable permission assignment; this helps with granting access to datasets by business classification, not allowing a controlled role to create tables in one registered S3 location.
D:Lake Formation supports fine-grained grants selecting only approved columns of governed tables; it would target preventing access to sensitive columns without copying datasets, while the question is about allowing a controlled role to create tables in one registered S3 location.
Question 367
An ETL run encounters malformed rows that require later correction and should not silently disappear. Where should they go?
- Quality quarantine S3 prefix
- DataBrew profile statistics
- Glue Data Quality ruleset
- DataBrew validation recipe
- Glue Data Quality evaluation results
Explanation
Correct Answer
A:A separate S3 prefix can preserve rejected records for controlled remediation without polluting curated queries; in this scenario, write structured rejection records to a secure quarantine location with error reason and source identifier.
Incorrect Answers
B:DataBrew profile jobs summarize null values, distributions and other properties of tabular input; this can support measuring baseline data characteristics before quality rule design, but would not address the need for keeping invalid records available for debugging but out of production analytics.
C:Glue Data Quality supports rulesets for evaluating data quality against supported datasets and ETL flows; this helps with applying repeatable quality checks in a Glue pipeline, not keeping invalid records available for debugging but out of production analytics.
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 keeping invalid records available for debugging but out of production analytics unmet.
E:Quality evaluation results record which configured checks pass and fail for a tested dataset; it would target tracking rule failures across successive daily runs, while the question is about keeping invalid records available for debugging but out of production analytics.
Question 368
A warehouse dimension changes daily but a nightly ETL recreates the whole table from source. What design reduces work?
- Redshift materialized view refresh
- Incremental ETL merge
- Spark broadcast join
- JDBC predicate pushdown
Explanation
Correct Answer
B:Incremental merges apply inserts and updates from new source changes instead of rebuilding the entire destination; in this scenario, carry change identifiers and upsert affected rows using a consistent key and checkpoint, including explicit delete handling if required.
Incorrect Answers
A:A materialized view stores precomputed query results that can be refreshed as base data changes; this can support accelerating repeated joins and aggregations for warehouse users, but would not address the need for processing only changed business records after an initial load.
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 processing only changed business records after an initial load unmet.
D:Source-side predicates can reduce rows transferred from a JDBC database into a distributed ETL job; it would target filtering historical relational data before network transfer, while the question is about processing only changed business records after an initial load.
Question 369
A production update might replace a stateful resource after a template revision. What should operators inspect first?
- CloudFormation change set
- AWS CDK construct
- AWS CloudFormation stack
- AWS SAM template
Explanation
Correct Answer
A:A change set previews proposed modifications to a stack before they are executed; in this scenario, create and review a change set to identify additions, replacements and deletions before authorizing the stack update.
Incorrect Answers
B:AWS CDK expresses cloud infrastructure using supported programming languages that synthesize CloudFormation; the current need is for reviewing potentially destructive infrastructure updates, not reusing programmable infrastructure definitions across teams.
C:CloudFormation provisions and updates AWS resources through declarative templates and stack change tracking; this can support recreating the same data pipeline infrastructure in different accounts, but would not address the need for reviewing potentially destructive infrastructure updates.
D:AWS SAM extends CloudFormation with serverless resource declarations for applications; this helps with packaging Lambda and Step Functions assets as serverless infrastructure, not reviewing potentially destructive infrastructure updates.
Question 370
A source account must reject S3 PutObject requests that omit required server-side encryption headers under the chosen design. What authorization technique helps?
- IAM policy condition key
- IAM permissions boundary
- IAM resource-scoped S3 policy
- IAM explicit deny precedence
Explanation
Correct Answer
A:IAM policy conditions can limit allowed API use based on supported request attributes and context; in this scenario, use supported S3 condition keys in the bucket or identity policy and test actual request headers rather than granting unconditional writes.
Incorrect Answers
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 restricting object writes to approved encryption settings 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 restricting object writes to approved encryption settings.
D:An explicit deny in an applicable policy overrides otherwise allowing IAM statements; its benefit is diagnosing access denied despite an Allow statement; that is different from restricting object writes to approved encryption settings.