Question 10
An audit needs GetObject activity for specific confidential buckets, not only bucket configuration changes. Which events should be recorded?
- CloudTrail management-event records
- CloudTrail log file integrity validation
- CloudTrail S3 object data events
- CloudTrail organization trail
Explanation
Correct Answer
C:CloudTrail can capture selected S3 object-level APIs as data events when explicitly configured; in this scenario, enable the required S3 data-event selection on a trail or event data store with suitable scope and retention.
Incorrect Answers
A:Management events track AWS control-plane actions such as PutBucketPolicy and CreateRole; it would target finding who changed resource permissions, while the question is about identifying who downloaded restricted data-lake objects.
B:Trail log file integrity validation provides digest files that can help detect tampering of delivered log files; its benefit is proving stored audit logs were not silently altered; that is different from identifying who downloaded restricted data-lake objects.
D:An organization trail can collect supported management activity centrally for accounts in an AWS Organization; this can support covering many accounts with one audit policy, but would not address the need for identifying who downloaded restricted data-lake objects.
Question 11
A data-release workflow calls an external validation service that may respond hours later and must not spin on repeated polls. Which pattern fits?
- Step Functions task token callback
- Glue workflow run properties
- Airflow catchup configuration
- EventBridge Scheduler retry policy
Explanation
Correct Answer
A:A task token lets a state-machine task wait for an external system to signal completion; in this scenario, pass a task token to the external worker and resume the execution only after it reports success or failure.
Incorrect Answers
B:Glue workflow run properties allow pipeline components to share run-scoped configuration values; its benefit is passing an ingestion batch identifier between Glue jobs; that is different from pausing a workflow for asynchronous external approval.
C:Airflow catchup behavior determines whether a DAG schedules missed historical intervals when enabled; the current need is for pausing a workflow for asynchronous external approval, not preventing a flood of old scheduled DAG runs.
D:Scheduler targets can have retry policies and dead-letter queue configuration for failed delivery attempts; this can support recovering from temporary failure to invoke a scheduled target, but would not address the need for pausing a workflow for asynchronous external approval.
Question 12
A supplier can only deliver encrypted files using SFTP and operations do not want to administer SSH servers. Which service fits?
- AWS DataSync transfer task
- S3 multipart upload
- AWS Transfer Family SFTP server
- AWS Snow Family offline transfer
Explanation
Correct Answer
C:Transfer Family exposes managed SFTP endpoints that can land partner files into S3 or EFS; in this scenario, configure a Transfer Family SFTP endpoint with backed storage and identities suited to the partner's authentication model.
Incorrect Answers
A:DataSync moves large datasets between supported on-premises or AWS storage locations with transfer management; this can support migrating terabytes from an on-premises file share into S3, but would not address the need for receiving external partner uploads over SFTP.
B:Multipart upload sends large objects as separately uploaded parts that can be retried independently; this helps with reliably uploading individual multi-gigabyte files over a variable connection, not receiving external partner uploads over SFTP.
D:Snow devices can support offline movement of large datasets when network bandwidth is inadequate; it would target seeding a cloud lake from a bandwidth-constrained site, while the question is about receiving external partner uploads over SFTP.
Question 13
A compliance team asks which original datasets contribute to a published finance dashboard. Which metadata capability helps?
- Job-run lineage metadata
- Column-level lineage mapping
- SageMaker Catalog lineage graph
- SageMaker ML Lineage Tracking
Explanation
Correct Answer
C:Catalog lineage can represent data assets and transformations to help trace upstream and downstream dependencies; in this scenario, capture asset relationships and transformation lineage so reviewers can follow the chain of source and derived data.
Incorrect Answers
A:Recording run identifiers, source versions and target outputs connects a materialized dataset to its producing workflow; this helps with auditing the exact files used in one derived table version, not tracing business report fields to source datasets.
B:Column-level lineage records how source fields produce downstream columns through transformations; although useful for determining whether a sensitive input field reaches a report column, it leaves the need for tracing business report fields to source datasets unmet.
D:ML lineage facilities can record relationships among model-development artifacts and processing steps; its benefit is tracing artifacts in a supported ML-related data preparation workflow; that is different from tracing business report fields to source datasets.
Question 14
An SQS worker processes messages for between one and twenty-five minutes; the original visibility period sometimes expires before a long task finishes. Permanently failing messages also need separate review. Which TWO controls address these requirements? Choose TWO.
- SQS ChangeMessageVisibility heartbeat
- Idempotent processing checkpoint
- SQS dead-letter queue
- Step Functions retry with backoff
- Multi-AZ dependent services
Explanation
Correct Answers
A:The SQS ChangeMessageVisibility API can dynamically extend the invisibility period of an in-flight message as a variable-length task proceeds; for the additional requirement of extending SQS visibility for a task whose running time varies widely, call ChangeMessageVisibility before the current interval ends during slow work, and delete the message only after successful processing; retain idempotency.
C:A dead-letter queue collects messages that repeatedly fail processing after configured receive attempts; in this scenario, configure an appropriate redrive policy so failed items move for inspection rather than being retried forever.
Incorrect Answers
B:Durable checkpoints plus idempotent sink writes limit duplicate effects after task retries; it would target making a restarted pipeline safe to replay, while the question is about isolating permanently failing messages for investigation.
D:State machine Retry rules can handle selected errors with intervals and exponential backoff; the current need is for isolating permanently failing messages for investigation, not recovering from transient downstream API failures.
E:Using supported multi-AZ data services can reduce interruption from a single Availability Zone failure; this can support keeping stateful dependencies available during one AZ outage, but would not address the need for isolating permanently failing messages for investigation.
Question 15
A producer already has a Redshift datashare containing approved financial tables. A new consumer account cannot use it because access to that account has not been granted. Which producer-side action is necessary?
- S3 access point scoped sharing
- Redshift producer datashare authorization
- Lake Formation cross-account sharing
- AWS Data Exchange subscription
Explanation
Correct Answer
B:Redshift producer administrators grant and authorize consumer access to datashares containing specified warehouse objects; in this scenario, add the approved consumer account to the datashare and authorize the consumer; the recipient can then set up its consumer database and access as permitted.
Incorrect Answers
A:S3 access points can provide separate access and network controls for applications using a common bucket; its benefit is sharing one lake bucket with several differently authorized applications; that is different from authorizing a new cross-account consumer of an existing Redshift datashare.
C:Lake Formation can govern cross-account catalog resource permissions for supported data-lake sharing workflows; this can support granting another account access to approved governed S3 tables, but would not address the need for authorizing a new cross-account consumer of an existing Redshift datashare.
D:AWS Data Exchange provides ways for subscribers to discover and access licensed third-party datasets; this helps with obtaining an external provider's licensed dataset under managed terms, not authorizing a new cross-account consumer of an existing Redshift datashare.
Question 16
Partners must request an individual report by ID over HTTPS with identity checks and request quotas. What entry point fits?
- S3 presigned GET URL
- API Gateway REST API integration
- Lambda query facade
- AppSync GraphQL resolver
Explanation
Correct Answer
B:API Gateway can expose authenticated HTTP methods that route to a backed data service; in this scenario, configure an API method and backend integration with authorization and throttling before returning only permitted report fields.
Incorrect Answers
A:A presigned S3 URL grants time-limited access to a specific object using the signer's permissions; the current need is for publishing filtered datasets through a governed API, not securely delivering a large generated report file.
C:A Lambda handler can validate inputs, query a datastore and serialize responses for API callers; this helps with hiding database credentials and SQL behind a service endpoint, not publishing filtered datasets through a governed API.
D:AppSync supports GraphQL operations with resolvers that access data sources; although useful for exposing a typed GraphQL interface to clients, it leaves the need for publishing filtered datasets through a governed API unmet.
Question 17
Analysts need to join a small Redshift dimension table to a year of Parquet events that must remain in S3. Which feature fits?
- Redshift datashare
- Redshift federated query
- Redshift materialized view
- Redshift Spectrum external tables
Explanation
Correct Answer
D:Redshift Spectrum queries external data in S3 via catalog-backed external table definitions; in this scenario, define external schemas and tables with appropriate catalog permissions, then query lake objects alongside local tables.
Incorrect Answers
A: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 S3 lake datasets without first loading them into warehouse tables.
B:Redshift federated query reads supported operational relational databases from analytic SQL; this helps with joining current operational rows from a supported database without bulk replication, not joining S3 lake datasets without first loading them into warehouse tables.
C:A materialized view persists computed query results for repeated retrieval and planned refresh; although useful for caching a recurring expensive analytic result inside the warehouse, it leaves the need for joining S3 lake datasets without first loading them into warehouse tables unmet.
Question 18
An engineer must find the principal that changed a stream's retention setting yesterday. Which event category fits?
- CloudTrail Lake event data store
- CloudTrail management events
- CloudTrail trail to S3
- CloudTrail S3 data events
Explanation
Correct Answer
B:Management events record control-plane API operations such as creating or updating AWS resources; in this scenario, review CloudTrail management events for the configuration API and correlate the invoking identity and request parameters.
Incorrect Answers
A:CloudTrail Lake stores queryable event data for SQL-based investigation over configured event sources; this can support searching years of selected API activity with SQL, but would not address the need for auditing who modified a Kinesis stream configuration.
C:An organization trail can deliver selected CloudTrail records to a centralized S3 destination for retention and auditing; although useful for consolidating API audit records from multiple accounts, it leaves the need for auditing who modified a Kinesis stream configuration unmet.
D:CloudTrail data events can record object-level operations for selected S3 resources when configured; it would target auditing individual object reads in a sensitive lake, while the question is about auditing who modified a Kinesis stream configuration.
Question 19
A fresh table contains possible negative quantities and the team needs an auditable count of such records. Which validation technique works?
- DataBrew missing-value transform
- Athena conditional validation SQL
- Notebook exploratory validation
- SageMaker Data Wrangler transformations
Explanation
Correct Answer
B:Athena SQL can detect rule violations using predicates and aggregations over cataloged data; in this scenario, run a filtered SQL count with documented validity rules and record results before marking the partition ready.
Incorrect Answers
A:DataBrew recipes support data cleaning operations for missing or inconsistent tabular field values; the current need is for quantifying invalid rows before publishing an S3 dataset, not standardizing blanks without custom ETL code.
C:Notebooks enable iterative code, plots and checks for exploratory analysis of sampled datasets; this helps with investigating anomalies with repeatable interactive code, not quantifying invalid rows before publishing an S3 dataset.
D: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 quantifying invalid rows before publishing an S3 dataset unmet.
Question 20
Two Kinesis analytics applications need separately registered consumer identities and dedicated shard read throughput so neither reader slows the other. Which TWO measures meet both needs? Choose TWO.
- SQS standard queue fan-in
- Kafka consumer groups
- Kinesis enhanced fan-out
- Kinesis partition key design
- Separate registered stream consumers
Explanation
Correct Answers
C:Enhanced fan-out gives registered consumers dedicated throughput for a Kinesis Data Streams shard; in this scenario, dedicated consumer throughput reduces interference; each registered reader can process at an independent rate while tracking its own position.
E:Applications can register distinct Kinesis stream consumers to obtain their own enhanced fan-out paths; for the additional requirement of creating separately managed read identities for independent applications, register independent consumer applications and map each to its own processing logic and permissions.
Incorrect Answers
A:A standard SQS queue buffers messages from multiple producers for a pool of competing worker consumers; this can support decoupling many asynchronous producers from workers, but would not address the need for isolating high-throughput independent stream readers.
B: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 isolating high-throughput independent stream readers.
D:A Kinesis partition key determines shard assignment and per-key ordering for records; it would target spreading heavy producer traffic across shards, while the question is about isolating high-throughput independent stream readers.