Question 310
A data lake landing prefix includes `_temporary` directories that should never influence catalog schemas. Which crawler setting helps?
- Custom Glue classifier
- Glue crawler schema inference
- Crawler schema change policy
- Crawler exclusion pattern
Explanation
Correct Answer
D:Crawler exclusions prevent matching paths and files from being considered during discovery; in this scenario, exclude staging and rejected paths so only intended data files contribute to the inferred dataset metadata.
Incorrect Answers
A:A custom classifier influences how Glue crawlers recognize certain input formats and extract schemas; the current need is for excluding temporary and rejected files from inferred tables, not correctly recognizing a nonstandard delimited text format.
B:A Glue crawler inspects supported source data and infers table structures for the Data Catalog; this can support discovering schemas from newly landed files, but would not address the need for excluding temporary and rejected files from inferred tables.
C:Crawler change policies control how discovered schema differences update catalog objects; this helps with preventing surprise schema rewrites from new vendor files, not excluding temporary and rejected files from inferred tables.
Question 311
A database's primary Region is compliant, but its automated cross-Region backups would violate contractual residency requirements. What design correction is necessary?
- Sovereignty-aware backup location
- AWS Config configuration history
- Amazon Macie S3 scan
- S3 replication Region restriction
Explanation
Correct Answer
A:Backup and restore destinations must respect organization-specific data sovereignty and retention obligations; in this scenario, configure backup copies and failover destinations only in permitted jurisdictions and verify service-specific replication controls.
Incorrect Answers
B:AWS Config records supported resource configurations and changes to help evaluate resource-state compliance; although useful for identifying when a bucket replication policy changed, it leaves the need for keeping disaster-recovery data inside approved jurisdictions unmet.
C:Macie sensitive-data discovery can identify candidate personal data and generate findings for supported S3 objects; it would target finding accidentally uploaded personal identifiers in an approved bucket, while the question is about keeping disaster-recovery data inside approved jurisdictions.
D:Replication configuration determines which destination bucket and Region receive copies of source objects; its benefit is preventing regulated object copies from entering a prohibited Region; that is different from keeping disaster-recovery data inside approved jurisdictions.
Question 312
A transactional database must fail over after an Availability Zone failure without manual snapshot restoration. Which RDS design fits?
- S3 cross-Region replication
- S3 same-Region replication
- DynamoDB global tables
- S3 Replication Time Control
- RDS Multi-AZ deployment
Explanation
Correct Answer
E:An RDS Multi-AZ deployment can provide a synchronized standby or multi-node configuration for availability; in this scenario, select a supported Multi-AZ deployment and test client reconnection, separating high availability from cross-Region disaster recovery.
Incorrect Answers
A:Cross-Region Replication asynchronously copies eligible objects between buckets in different AWS Regions; although useful for protecting approved datasets with a second-Region object copy, it leaves the need for maintaining database availability through a single-AZ outage unmet.
B:Same-Region Replication copies eligible objects between buckets within one Region for supported uses; it would target maintaining a second bucket copy without crossing residency boundaries, while the question is about maintaining database availability through a single-AZ outage.
C:Global tables replicate DynamoDB table items across selected AWS Regions for multi-Region application access; its benefit is providing regional writes and resilient access to key-value data; that is different from maintaining database availability through a single-AZ outage.
D:S3 Replication Time Control provides an SLA-backed replication-time target and metrics for eligible replication rules; the current need is for maintaining database availability through a single-AZ outage, not monitoring time-bounded cross-Region replication.
Question 313
An AWS-managed service cannot complete setup because a required service-linked role was deleted. Which identity artifact should be restored?
- SageMaker Unified Studio project membership
- Service-linked IAM role
- SageMaker Unified Studio domain
- IAM managed versus inline policy
- SageMaker domain unit hierarchy
- IAM identity policy attachment
Explanation
Correct Answer
B:Service-linked roles are IAM roles predefined for supported AWS services to act on an account's behalf; in this scenario, recreate the documented service-linked role through the service's supported setup flow rather than giving it administrator access.
Incorrect Answers
A:Project membership controls collaboration and access within the project's governed workspace; it would target limiting an analyst's membership to one approved project, while the question is about allowing an AWS managed service to perform its own required operations.
C:A Unified Studio domain defines an overarching environment for governed data and analytics workspaces; the current need is for allowing an AWS managed service to perform its own required operations, not establishing a common organizational boundary for governed projects.
D:Customer-managed IAM policies can be versioned and reused across roles, unlike role-specific inline policies; this can support reusing controlled permissions across multiple data pipeline roles, but would not address the need for allowing an AWS managed service to perform its own required operations.
E:Domain units group related teams and help structure delegated governance within a domain; this helps with separating business-unit stewardship responsibilities, not allowing an AWS managed service to perform its own required operations.
F:An identity-based IAM policy grants allowed API actions to a user, group or role subject to other policy checks; although useful for authorizing a data-processing role for a narrow AWS API action, it leaves the need for allowing an AWS managed service to perform its own required operations unmet.
Question 314
A DynamoDB table is keyed by device ID, but users must efficiently list items by tenant ID. Which feature provides that access path?
- DynamoDB global secondary index
- DynamoDB composite key
- Redshift sort key selection
- RDS secondary B-tree index
Explanation
Correct Answer
A:A GSI supports queries using an alternate partition/sort key without changing the table's primary key; in this scenario, create a suitable GSI keyed on tenant ID and project the attributes callers require, accounting for added write and storage costs.
Incorrect Answers
B:DynamoDB partition and sort keys efficiently organize related items for a known query access pattern; this helps with retrieving the latest orders for one account, not querying DynamoDB items by a second business identifier.
C:Redshift sort keys can improve block elimination for queries filtering on correlated column values; although useful for reducing scanned blocks for frequent time-range queries, it leaves the need for querying DynamoDB items by a second business identifier unmet.
D:A relational secondary index can accelerate selective predicates when its maintenance cost is justified; it would target accelerating indexed equality lookups on a relational table, while the question is about querying DynamoDB items by a second business identifier.
Question 315
A research group needs years of immutable log archives and images for future exploratory processing. Which storage foundation fits?
- Amazon DynamoDB table
- Amazon Redshift warehouse
- Amazon S3 data lake
- Amazon RDS relational database
Explanation
Correct Answer
C:S3 stores durable objects of varying formats economically without requiring an operational database schema; in this scenario, keep the source data as objects with appropriate lifecycle and cataloging; query engines can be attached independently later.
Incorrect Answers
A:DynamoDB provides managed key-value and document access at low latency using partition keys and indexes; this can support serving predictable millisecond item lookups at high request volume, but would not address the need for retaining raw petabyte-scale historical source files.
B:Redshift offers columnar analytic processing for large SQL aggregations over warehouse datasets; this helps with executing repeated analytical joins over large fact tables, not retaining raw petabyte-scale historical source files.
D:Amazon RDS manages supported relational engines for transactional workloads using SQL and constraints; it would target supporting ACID transactions across related business records, while the question is about retaining raw petabyte-scale historical source files.
Question 316
Large fact tables already reside in Redshift and require a scheduled aggregation into a reporting table. What processing style reduces unnecessary movement?
- AWS Glue Spark ETL
- Lambda per-record enrichment
- Amazon EMR customized frameworks
- Redshift SQL transformations
Explanation
Correct Answer
D:Redshift SQL operations can transform warehouse-resident data without exporting it to a separate engine; in this scenario, run SQL transformations within Redshift, using appropriate workload management and transaction controls for the table load.
Incorrect Answers
A:AWS Glue provides managed Spark-based ETL jobs and integration with the Data Catalog; although useful for running recurring serverless-style Spark transformations, it leaves the need for reshaping existing warehouse tables in place unmet.
B:Lambda is suited to short event-driven transformations within its runtime and resource limits; it would target enriching individual small records after an event, while the question is about reshaping existing warehouse tables in place.
C:Amazon EMR provides controlled Hadoop and Spark clusters with configurable frameworks and libraries; its benefit is running specialized large-scale distributed transformations; that is different from reshaping existing warehouse tables in place.
Question 317
A dashboard issues repetitive slow database queries whenever users change filters and data freshness can be scheduled. What QuickSight dataset mode helps?
- DataBrew visual profiling
- Amazon QuickSight dashboard
- Athena result visualization downstream
- QuickSight SPICE dataset
Explanation
Correct Answer
D:SPICE provides in-memory accelerated storage for supported QuickSight analytic datasets; in this scenario, import an appropriately sized dataset into SPICE and set refresh cadence while accounting for available capacity.
Incorrect Answers
A:DataBrew's visual interface can inspect column distributions and transformations before publishing cleaned output; although useful for exploring raw field problems interactively, it leaves the need for speeding repeated dashboard interactions on imported results unmet.
B:QuickSight builds governed analytic dashboards and visualizations from configured data sources; it would target publishing metrics to business users through dashboards, while the question is about speeding repeated dashboard interactions on imported results.
C:Athena produces query result datasets that can be connected to separate reporting and visualization tools; its benefit is preparing lake queries for a dashboard dataset; that is different from speeding repeated dashboard interactions on imported results.
Question 318
A Glue job started timing out after inputs doubled, and operators must distinguish resource pressure from scheduling delay. What measurements help?
- Glue job run metrics
- Step Functions failed state details
- MWAA scheduler log
- MWAA worker task log
Explanation
Correct Answer
A:Glue job run data includes execution duration, failures and relevant service metrics for job diagnosis; in this scenario, compare job run duration, worker utilization, input volume and executor logs before deciding on capacity changes.
Incorrect Answers
B:Execution details identify state-level errors and task transitions in a Step Functions workflow; this can support locating which branch and integration caused a state-machine failure, but would not address the need for determining whether an ETL problem is resource-related.
C:Scheduler logs show why Apache Airflow DAG runs may not be getting scheduled; this helps with diagnosing DAG runs that never enter the queue, not determining whether an ETL problem is resource-related.
D:Worker task logs record errors raised while an Airflow operator executes; although useful for diagnosing a failed task with running schedulers, it leaves the need for determining whether an ETL problem is resource-related unmet.
Question 319
Developers copy changed scripts manually to production after successful testing in staging. Which release principle improves reproducibility?
- Immutable deployment artifact
- Unit tests with fixture data
- Git pull request review
- CI pipeline integration tests
Explanation
Correct Answer
A:Versioned packages and immutable images let a pipeline redeploy the exact artifact tested previously; in this scenario, promote the same versioned artifact across environments and use configuration parameters for environment-specific settings.
Incorrect Answers
B:Unit tests validate transformation functions against representative inputs and expected results; although useful for catching mapping regressions before deployment, it leaves the need for preventing drift between staging and production ETL code unmet.
C:Git branches and pull requests support code review before changes merge into a shared baseline; it would target reviewing ETL changes before production release, while the question is about preventing drift between staging and production ETL code.
D:Integration tests exercise real interfaces between components in an isolated environment; its benefit is validating source-to-target contracts before release; that is different from preventing drift between staging and production ETL code.
Question 320
A Lambda handler succeeds, but users report events being processed minutes after publication. Which metric shows consumer delay?
- Kinesis iterator age metric
- Lambda batch failure reporting
- Lambda parallelization factor
- Kinesis event source mapping
Explanation
Correct Answer
A:IteratorAge measures how far behind a stream-reading Lambda consumer is in processing records; in this scenario, monitor the function's iterator age alongside errors and duration to distinguish falling behind from producer-side arrival gaps.
Incorrect Answers
B:Lambda can report individual failed record IDs for supported stream batch processing; its benefit is retrying only failed records in a stream batch; that is different from diagnosing lag in a Lambda stream consumer.
C:The parallelization factor raises concurrent Lambda batches processed per Kinesis shard while preserving partition-key ordering; the current need is for diagnosing lag in a Lambda stream consumer, not increasing consumer throughput on busy shards.
D:A Lambda event source mapping reads Kinesis records, checkpoints progress and invokes the function in batches; this can support connecting a Lambda processor to a Kinesis shard, but would not address the need for diagnosing lag in a Lambda stream consumer.