Question 110
A report must combine Redshift history with a small, live PostgreSQL table that cannot be copied nightly. What access mechanism helps?
- Redshift federated query
- Redshift materialized view
- Redshift Spectrum external tables
- Redshift datashare
Explanation
Correct Answer
A:Redshift federated query reads supported operational relational databases from analytic SQL; in this scenario, query the supported external database through a federated schema and limit remote reads to avoid overloading the source.
Incorrect Answers
B:A materialized view persists computed query results for repeated retrieval and planned refresh; its benefit is caching a recurring expensive analytic result inside the warehouse; that is different from joining current operational rows from a supported database without bulk replication.
C:Redshift Spectrum queries external data in S3 via catalog-backed external table definitions; the current need is for joining current operational rows from a supported database without bulk replication, not joining S3 lake datasets without first loading them into warehouse tables.
D:Redshift data sharing lets authorized consumers query shared warehouse data without making full copies; this can support exposing governed datasets to a separate Redshift consumer, but would not address the need for joining current operational rows from a supported database without bulk replication.
Question 111
Auditors need evidence of which role downloaded particular sensitive S3 objects, not just who changed bucket policies. What should be enabled?
- CloudTrail management events
- CloudTrail Lake event data store
- CloudTrail S3 data events
- CloudTrail trail to S3
Explanation
Correct Answer
C:CloudTrail data events can record object-level operations for selected S3 resources when configured; in this scenario, configure object-level data-event logging for the intended bucket scope and route trail output to a protected log destination.
Incorrect Answers
A:Management events record control-plane API operations such as creating or updating AWS resources; it would target auditing who modified a Kinesis stream configuration, while the question is about auditing individual object reads in a sensitive lake.
B:CloudTrail Lake stores queryable event data for SQL-based investigation over configured event sources; its benefit is searching years of selected API activity with SQL; that is different from auditing individual object reads in a sensitive lake.
D:An organization trail can deliver selected CloudTrail records to a centralized S3 destination for retention and auditing; this can support consolidating API audit records from multiple accounts, but would not address the need for auditing individual object reads in a sensitive lake.
Question 112
Supplier data uses empty strings, 'N/A' and null inconsistently across columns. What preparation approach helps?
- SageMaker Data Wrangler transformations
- Athena conditional validation SQL
- Notebook exploratory validation
- DataBrew missing-value transform
Explanation
Correct Answer
D:DataBrew recipes support data cleaning operations for missing or inconsistent tabular field values; in this scenario, apply field-specific normalization rules in a recipe and preserve the distinction between unknown and legitimately empty values.
Incorrect Answers
A:Data Wrangler offers visual data preparation transformations in supported SageMaker data workflows; although useful for preparing features or exploratory datasets through a visual workflow, it leaves the need for standardizing blanks without custom ETL code unmet.
B:Athena SQL can detect rule violations using predicates and aggregations over cataloged data; it would target quantifying invalid rows before publishing an S3 dataset, while the question is about standardizing blanks without custom ETL code.
C:Notebooks enable iterative code, plots and checks for exploratory analysis of sampled datasets; its benefit is investigating anomalies with repeatable interactive code; that is different from standardizing blanks without custom ETL code.
Question 113
New real-time fraud and reporting applications must read the same stream without coordinating a shared consumer state. What setup is appropriate?
- Separate registered stream consumers
- Kinesis enhanced fan-out
- SQS standard queue fan-in
- Kinesis partition key design
- Kafka consumer groups
Explanation
Correct Answer
A:Applications can register distinct Kinesis stream consumers to obtain their own enhanced fan-out paths; in this scenario, register independent consumer applications and map each to its own processing logic and permissions.
Incorrect Answers
B:Enhanced fan-out gives registered consumers dedicated throughput for a Kinesis Data Streams shard; its benefit is isolating high-throughput independent stream readers; that is different from creating separately managed read identities for independent applications.
C:A standard SQS queue buffers messages from multiple producers for a pool of competing worker consumers; the current need is for creating separately managed read identities for independent applications, not decoupling many asynchronous producers from workers.
D:A Kinesis partition key determines shard assignment and per-key ordering for records; this can support spreading heavy producer traffic across shards, but would not address the need for creating separately managed read identities for independent applications.
E:Kafka consumer groups divide topic partitions among members within a group while different groups read independently; this helps with scaling workers for one Kafka subscription, not creating separately managed read identities for independent applications.
Question 114
A warehouse report needs each sensor row with a seven-reading rolling mean, not one row per sensor. Which SQL feature fits?
- Redshift SQL window function
- SQL PIVOT transformation
- SQL GROUP BY aggregate
- Athena SQL view
Explanation
Correct Answer
A:Window functions calculate values across related rows while preserving row-level output; in this scenario, use a window partition and ordered frame so each row receives the intended rolling aggregate.
Incorrect Answers
B:Pivoting turns distinct category values into separate columns for cross-tab reports in supported SQL engines; this can support presenting monthly category totals as columns, but would not address the need for computing a rolling average for each device.
C:GROUP BY collapses input rows into groups and computes aggregate measures per distinct key; this helps with producing daily totals per store, not computing a rolling average for each device.
D:An Athena view stores a query definition for reuse over underlying tables; although useful for exposing a stable SQL projection over lake data, it leaves the need for computing a rolling average for each device unmet.
Question 115
A synchronous ingestion API has unpredictable initialization latency after idle periods. Which Lambda feature may reduce that?
- Lambda memory/CPU setting
- Provisioned concurrency
- Lambda asynchronous invocation destinations
- Reserved concurrency
Explanation
Correct Answer
B:Provisioned concurrency pre-initializes a configured number of Lambda execution environments to reduce cold-start delay; in this scenario, keep provisioned environments warm for the expected demand, while measuring added cost and burst behavior.
Incorrect Answers
A:Lambda allocates more CPU capacity as the configured memory size increases; this can support speeding CPU-intensive parsing in a Lambda transform, but would not address the need for stabilizing low-latency synchronous API responses.
C:Lambda asynchronous destinations can send execution success or failure records to supported targets; although useful for recording failed asynchronous enrichments for repair, it leaves the need for stabilizing low-latency synchronous API responses unmet.
D:Reserved concurrency allocates a concurrency limit and reservation to a specific Lambda function; it would target protecting a downstream database from too many simultaneous function calls, while the question is about stabilizing low-latency synchronous API responses.
Question 116
A data team wants invoice and supplier tables grouped under one schema-like name for Athena users. Which organizational object fits?
- Athena named database
- Data Catalog table version history
- Glue partition metadata
- Glue Data Catalog table
Explanation
Correct Answer
A:An Athena database is a logical namespace for tables in the underlying catalog; in this scenario, create or use an appropriate catalog database and grant access to its tables; the namespace does not hold the data files.
Incorrect Answers
B:Data Catalog versions can preserve prior table metadata definitions for certain schema-management workflows; although useful for inspecting a prior table schema after a crawler update, it leaves the need for organizing named datasets for a SQL workgroup unmet.
C:Catalog partition definitions map partition values to locations so compatible engines can prune object sets; it would target registering new date partitions before reading them, while the question is about organizing named datasets for a SQL workgroup.
D:A Data Catalog table describes a dataset's location, columns and serialization for compatible query engines; its benefit is sharing an S3 table definition across Athena and Glue; that is different from organizing named datasets for a SQL workgroup.
Question 117
A stream's iterator age rises briefly during normal maintenance but should page only when errors are also elevated. What alarm design fits?
- CloudWatch alarm evaluation periods
- SNS subscription filtering
- EventBridge failed-event DLQ
- CloudWatch alarm composite
Explanation
Correct Answer
D:Composite alarms combine the states of other alarms using logical expressions; in this scenario, combine relevant alarms to reduce noise while still retaining the underlying diagnostic metrics.
Incorrect Answers
A:Alarm evaluation periods govern how many datapoints must breach a threshold before the alarm changes state; this helps with suppressing alerts for harmless single-sample spikes, not paging only when error rate and backlog are both unhealthy.
B:SNS subscription filter policies select which topic messages are delivered to specific subscribers; although useful for routing alerts by data pipeline ownership, it leaves the need for paging only when error rate and backlog are both unhealthy unmet.
C:A rule target can use an SQS dead-letter queue to retain undelivered events after retry exhaustion; it would target capturing notifications that fail delivery to the target, while the question is about paging only when error rate and backlog are both unhealthy.
Question 118
A parser tests each transaction ID against a long Python list and spends most runtime on membership scans. What data structure helps?
- Vectorized dataframe operation
- SQL predicate pushdown
- Chunked iterator processing
- Set membership lookup
Explanation
Correct Answer
D:Hash-based set membership generally offers efficient repeated presence checks in memory; in this scenario, build a set of eligible IDs, accepting memory cost to avoid repeatedly scanning the entire list.
Incorrect Answers
A:Vectorized data operations process columns or batches without per-row interpreter overhead; although useful for reducing per-row Python transformation overhead, it leaves the need for accelerating millions of repeated key lookups unmet.
B:Predicate pushdown filters eligible records near the source and reduces data moved for ETL; it would target avoiding needless rows in a JDBC extraction, while the question is about accelerating millions of repeated key lookups.
C:Chunking processes large inputs in bounded pieces rather than loading an entire dataset into memory; its benefit is reading multi-gigabyte files within tight memory limits; that is different from accelerating millions of repeated key lookups.
Question 119
A Glue crawler can discover a table, but the subsequent ETL job cannot read the data objects. Which principal is central to that job's API access?
- Secrets Manager scheduled rotation
- STS AssumeRole for cross-account processing
- Glue job service role
- Lambda execution IAM role
Explanation
Correct Answer
C:A Glue job runs with an IAM role that authorizes its data, catalog and logging operations; in this scenario, examine the Glue job role's permissions, as crawler privileges are not automatically granted to a distinct ETL role.
Incorrect Answers
A:Secrets Manager rotation workflows can update supported credentials and associated secret versions; this can support rotating a relational password without embedding updates in code, but would not address the need for enabling Glue to access controlled catalog and S3 resources.
B:STS AssumeRole returns temporary credentials for an authorized role trust relationship; this helps with allowing an ETL account to read a partner account's approved objects, not enabling Glue to access controlled catalog and S3 resources.
D:Lambda assumes its execution role to call permitted AWS APIs during function invocation; it would target granting Lambda controlled read access to one S3 prefix, while the question is about enabling Glue to access controlled catalog and S3 resources.
Question 120
An ETL process already lives in AWS Glue and simply needs to run every six hours. Which native scheduling feature can initiate it?
- Step Functions with EventBridge rule
- Amazon MWAA DAG schedule
- EventBridge Scheduler
- Glue job trigger schedule
Explanation
Correct Answer
D:Glue scheduled triggers start designated Glue jobs according to a configured schedule; in this scenario, use a scheduled Glue trigger for the job; it is adequate when no complex cross-service dependencies are required.
Incorrect Answers
A:An EventBridge scheduled rule can initiate a Step Functions state machine execution; the current need is for running a single Glue ETL job on a fixed cadence, not periodically invoking a multi-step serverless data workflow.
B:An Airflow DAG schedule defines recurring execution of an orchestration graph in Amazon MWAA; this can support scheduling a dependency-aware Airflow workflow, but would not address the need for running a single Glue ETL job on a fixed cadence.
C:EventBridge Scheduler invokes supported targets on configured schedules with time-zone options; this helps with launching a daily transform at a specified local time, not running a single Glue ETL job on a fixed cadence.