Question 80
A Python inventory program lists only the first thousand S3 objects and silently misses the rest. What SDK feature should be used?
- API response pagination contract
- ECS task role credential provider
- SDK client retry configuration
- Boto3 paginator
Explanation
Correct Answer
D:Boto3 paginators iterate AWS API responses that return continuation tokens and limited pages; in this scenario, iterate all result pages with a paginator or continuation token; one API response is not necessarily the complete collection.
Incorrect Answers
A: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 retrieving every object across paginated AWS API responses unmet.
B:The AWS SDK credential provider chain can obtain short-lived task-role credentials from an Amazon ECS task identity without static keys; it would target authenticating a scheduled ECS data-container AWS SDK client without static keys, while the question is about retrieving every object across paginated AWS API responses.
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 retrieving every object across paginated AWS API responses.
Question 81
Temporary analytics exports must be removed automatically after ninety days unless a separate hold applies. Which S3 feature fits?
- S3 Object Lock retention
- S3 Lifecycle noncurrent expiration
- S3 Lifecycle expiration
- S3 Lifecycle abort multipart upload
Explanation
Correct Answer
C:Lifecycle expiration removes eligible objects automatically after conditions such as object age are met; in this scenario, apply an expiration rule to the relevant prefix or tags and confirm interactions with versioning and retention requirements.
Incorrect Answers
A:S3 Object Lock enforces supported retention controls that can prevent object deletion during required periods; it would target retaining evidence against premature deletion, while the question is about deleting obsolete unversioned objects after a retention interval.
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 deleting obsolete unversioned objects after a retention interval.
D:A lifecycle rule can remove incomplete multipart-upload parts after a configured age; this can support preventing orphaned upload parts from accumulating charges, but would not address the need for deleting obsolete unversioned objects after a retention interval.
Question 82
A customer dimension feed includes some rows without customer_id, making future joins unreliable. What quality check is essential?
- Non-null primary field check
- Allowed-value domain check
- Uniqueness constraint test
- Cross-field consistency check
Explanation
Correct Answer
A:Non-null validation checks reject or quarantine records missing mandatory business identifiers; in this scenario, validate the identifier before publish and send failing rows to a quarantined dataset for correction.
Incorrect Answers
B:Domain checks ensure values belong to documented categories or ranges rather than arbitrary strings; although useful for rejecting unsupported transaction status codes, it leaves the need for preventing records without required identifiers entering a curated table unmet.
C:Uniqueness checks detect duplicate keys within a dataset or business partition; it would target identifying duplicate order IDs after source replay, while the question is about preventing records without required identifiers entering a curated table.
D:Cross-field validation evaluates relationships between columns rather than judging each field alone; its benefit is detecting logical contradictions in financial records; that is different from preventing records without required identifiers entering a curated table.
Question 83
An analytics account must begin reading SSE-KMS-encrypted objects in a partner S3 bucket; currently no cross-account S3 or KMS permissions are granted. Which THREE authorization layers must be configured? Choose THREE.
- TLS for JDBC connections
- External role IAM KMS permission
- Cross-account KMS key policy
- Client-side encryption before upload
- Cross-account S3 bucket policy
Explanation
Correct Answers
B:A consumer identity policy can permit use of an externally owned customer-managed KMS key when its key policy also allows it; for the additional requirement of enabling a cross-account reader role to call KMS Decrypt, add scoped KMS permissions on the designated key to the role, respecting resource policies and organization restrictions.
C:A customer-managed KMS key policy can authorize a principal or external account for intended cryptographic operations; in this scenario, the key owner must permit appropriate cross-account key use, with the consumer's IAM permissions and S3 access aligned.
E:An S3 resource policy can authorize an external principal to read particular object keys; for the additional requirement of allowing a partner role to reach shared encrypted object paths, grant the designated external principal the needed S3 read operations on the shared prefix, with any required listing scope.
Incorrect Answers
A:TLS secures supported database client-server communications against interception in transit; it would target encrypting traffic from Glue to a relational database endpoint, while the question is about granting a partner account permitted access to encrypted lake objects.
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 granting a partner account permitted access to encrypted lake objects.
Question 84
An embedding store needs low-latency approximate nearest-neighbor results with an index that may consume substantial memory. Which index family fits?
- Exact vector similarity scan
- Vector index recall tuning
- IVF vector clustering
- HNSW approximate index
Explanation
Correct Answer
D:HNSW organizes vectors in a navigable proximity graph for approximate nearest-neighbor retrieval; in this scenario, hNSW navigates graph neighbors rather than scanning every vector; tune construction and search parameters against recall and resource use.
Incorrect Answers
A:Exact similarity evaluates distances against all relevant embeddings rather than using approximate pruning; its benefit is obtaining an exact ranking for a small embedding collection; that is different from favoring search speed and recall in large vector indexes.
B:Recall measures how often approximate search finds neighbors present in an exact reference result set; the current need is for favoring search speed and recall in large vector indexes, 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 favoring search speed and recall in large vector indexes.
Question 85
A Glue job doubled in data volume: Spark stage metrics show executor memory pressure, and only a few oversized input partitions keep most workers idle. Which TWO changes directly address those bottlenecks? Choose TWO.
- Glue job bookmark reset
- Glue job data partition tuning
- EMR step logs in S3
- EMR managed scaling policies
- Glue job worker increase
Explanation
Correct Answers
B:Spark partition sizing determines whether distributed ETL tasks can run evenly and make good use of available executor slots; for the additional requirement of raising parallel task utilization when a Glue read produces too few partitions, increase appropriately balanced input or shuffle partition counts and check file sizes and task metrics so workers can run partitions concurrently.
E:More appropriate Glue worker resources can help when Spark tasks are genuinely CPU or memory constrained; in this scenario, increase suitable worker capacity after profiling, then compare run cost and processing time rather than blindly adding resources.
Incorrect Answers
A:Resetting a Glue bookmark permits an ETL job to reprocess previously tracked source data intentionally; although useful for replaying a corrected historical data batch, it leaves the need for reducing a resource-limited Glue job runtime unmet.
C:EMR cluster logging can preserve step and application output in an S3 log destination; its benefit is investigating a failed historical EMR processing step; that is different from reducing a resource-limited Glue job runtime.
D:EMR managed scaling adjusts available node capacity under configured bounds for supported clusters; the current need is for reducing a resource-limited Glue job runtime, not matching variable Spark compute demand without constant oversizing.
Question 86
A Glue job suddenly uses a different worker count and an auditor needs the caller and time of the update API. What source helps?
- DMS task logs
- S3 server access logging
- Redshift system query logs
- CloudTrail event history
Explanation
Correct Answer
D:CloudTrail event history exposes recent management activity for an account within its documented retention; in this scenario, examine management-event history for the job update and associated identity rather than looking only at ETL application logs.
Incorrect Answers
A:DMS task logs record migration and change-capture operational events and diagnostic details; its benefit is diagnosing failed replication-table mappings; that is different from tracing who changed a Glue job configuration recently.
B:S3 server access logs can record requests made to a bucket and deliver log files to a chosen destination; the current need is for tracing who changed a Glue job configuration recently, not reviewing bucket request activity in a storage-focused audit.
C:Redshift query and system logging views provide evidence about SQL execution and warehouse operations; this can support tracing an unexpectedly expensive warehouse query, but would not address the need for tracing who changed a Glue job configuration recently.
Question 87
An Athena user sees a governed dataset but cannot query it due to insufficient data-lake permissions. What permission is needed?
- Lake Formation data location permissions
- Lake Formation column permissions
- Lake Formation table SELECT
- Lake Formation LF-Tag permissions
Explanation
Correct Answer
C:Lake Formation grants can authorize SQL SELECT access on governed catalog tables for supported integrations; in this scenario, grant the principal appropriate Lake Formation permissions on the database/table resources and verify underlying service integration.
Incorrect Answers
A: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 granting analysts read access to approved lake tables.
B:Lake Formation supports fine-grained grants selecting only approved columns of governed tables; its benefit is preventing access to sensitive columns without copying datasets; that is different from granting analysts read access to approved lake tables.
D: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 granting analysts read access to approved lake tables.
Question 88
Before enabling daily quality gates, a team must profile unknown source-field distributions and then enforce non-null and uniqueness rules within Glue ETL. Which TWO capabilities are required? Choose TWO.
- Glue Data Quality evaluation results
- DataBrew profile statistics
- Glue Data Quality ruleset
- Quality quarantine S3 prefix
- DataBrew validation recipe
Explanation
Correct Answers
B:DataBrew profile jobs summarize null values, distributions and other properties of tabular input; for the additional requirement of measuring baseline data characteristics before quality rule design, generate a data profile and review completeness and distributions before committing to an enforceable ruleset.
C:Glue Data Quality supports rulesets for evaluating data quality against supported datasets and ETL flows; in this scenario, define an AWS Glue Data Quality ruleset and run evaluations in the data pipeline before downstream publication.
Incorrect Answers
A:Quality evaluation results record which configured checks pass and fail for a tested dataset; although useful for tracking rule failures across successive daily runs, it leaves the need for applying repeatable quality checks in a Glue pipeline unmet.
D:A separate S3 prefix can preserve rejected records for controlled remediation without polluting curated queries; the current need is for applying repeatable quality checks in a Glue pipeline, not keeping invalid records available for debugging but out of production analytics.
E:A DataBrew recipe records transformations that can normalize inconsistent values and produce an approved output; this can support standardizing known fields before final quality evaluation, but would not address the need for applying repeatable quality checks in a Glue pipeline.
Question 89
Glue reads an entire 800-million-row table only to keep last week's records. Which optimization should be tested?
- JDBC predicate pushdown
- Spark broadcast join
- Redshift materialized view refresh
- Incremental ETL merge
Explanation
Correct Answer
A:Source-side predicates can reduce rows transferred from a JDBC database into a distributed ETL job; in this scenario, apply compatible query predicates at the database source, ensuring indexed filters and acceptable source load.
Incorrect Answers
B:A broadcast join sends a small relation to worker nodes to avoid shuffling both sides of a join; its benefit is reducing shuffle overhead when one lookup table is tiny; that is different from filtering historical relational data before network transfer.
C:A materialized view stores precomputed query results that can be refreshed as base data changes; the current need is for filtering historical relational data before network transfer, not accelerating repeated joins and aggregations for warehouse users.
D:Incremental merges apply inserts and updates from new source changes instead of rebuilding the entire destination; this can support processing only changed business records after an initial load, but would not address the need for filtering historical relational data before network transfer.
Question 90
A small data API uses Lambda and an API Gateway route, and developers want concise repeatable deployments. What framework fits?
- AWS CDK construct
- AWS CloudFormation stack
- CloudFormation change set
- AWS SAM template
Explanation
Correct Answer
D:AWS SAM extends CloudFormation with serverless resource declarations for applications; in this scenario, declare the serverless resources in a SAM template, build dependencies and deploy through the managed CloudFormation stack.
Incorrect Answers
A:AWS CDK expresses cloud infrastructure using supported programming languages that synthesize CloudFormation; this helps with reusing programmable infrastructure definitions across teams, not packaging Lambda and Step Functions assets as serverless infrastructure.
B:CloudFormation provisions and updates AWS resources through declarative templates and stack change tracking; although useful for recreating the same data pipeline infrastructure in different accounts, it leaves the need for packaging Lambda and Step Functions assets as serverless infrastructure unmet.
C:A change set previews proposed modifications to a stack before they are executed; it would target reviewing potentially destructive infrastructure updates, while the question is about packaging Lambda and Step Functions assets as serverless infrastructure.