Question 380
A critical S3 replication workflow needs measurable replication latency commitments rather than best-effort timing. What feature should be evaluated?
- DynamoDB global tables
- RDS Multi-AZ deployment
- S3 Replication Time Control
- S3 same-Region replication
- S3 cross-Region replication
Explanation
Correct Answer
C:S3 Replication Time Control provides an SLA-backed replication-time target and metrics for eligible replication rules; in this scenario, configure RTC on the relevant replication rule and monitor replication latency metrics for eligible objects.
Incorrect Answers
A: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 monitoring time-bounded cross-Region replication.
B:An RDS Multi-AZ deployment can provide a synchronized standby or multi-node configuration for availability; the current need is for monitoring time-bounded cross-Region replication, not maintaining database availability through a single-AZ outage.
D:Same-Region Replication copies eligible objects between buckets within one Region for supported uses; this helps with maintaining a second bucket copy without crossing residency boundaries, not monitoring time-bounded cross-Region replication.
E: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 monitoring time-bounded cross-Region replication unmet.
Question 381
A data engineer can authenticate through a role but receives AccessDenied for one required Glue GetJob call. What should be evaluated?
- IAM identity policy attachment
- SageMaker Unified Studio project membership
- SageMaker domain unit hierarchy
- SageMaker Unified Studio domain
- IAM managed versus inline policy
- Service-linked IAM role
Explanation
Correct Answer
A:An identity-based IAM policy grants allowed API actions to a user, group or role subject to other policy checks; in this scenario, add the minimum action and relevant resource scope to the role policy, considering permission boundaries and explicit denies.
Incorrect Answers
B:Project membership controls collaboration and access within the project's governed workspace; this can support limiting an analyst's membership to one approved project, but would not address the need for authorizing a data-processing role for a narrow AWS API action.
C:Domain units group related teams and help structure delegated governance within a domain; this helps with separating business-unit stewardship responsibilities, not authorizing a data-processing role for a narrow AWS API action.
D:A Unified Studio domain defines an overarching environment for governed data and analytics workspaces; although useful for establishing a common organizational boundary for governed projects, it leaves the need for authorizing a data-processing role for a narrow AWS API action unmet.
E:Customer-managed IAM policies can be versioned and reused across roles, unlike role-specific inline policies; it would target reusing controlled permissions across multiple data pipeline roles, while the question is about authorizing a data-processing role for a narrow AWS API action.
F:Service-linked roles are IAM roles predefined for supported AWS services to act on an account's behalf; its benefit is allowing an AWS managed service to perform its own required operations; that is different from authorizing a data-processing role for a narrow AWS API action.
Question 382
A data lake includes uploads from many departments and security must locate objects containing possible personal identifiers. Which discovery service helps?
- Amazon Macie sensitive data discovery
- Redshift dynamic data masking
- Deterministic PII tokenization
- One-way hashing of identifiers
- Data anonymization aggregation
Explanation
Correct Answer
A:Macie can examine supported S3 data for sensitive information and report discovery findings; in this scenario, use Macie sensitive-data discovery on selected S3 resources and route findings to remediation, respecting access and supported file types.
Incorrect Answers
B:Masking policies can return altered column representations to database users based on defined privileges; this helps with obscuring sensitive fields at query time for nonprivileged roles, not detecting unexpected sensitive content in S3 objects.
C:Tokenization replaces sensitive identifiers with controlled surrogate values and protects the mapping separately; although useful for linking customer events without exposing raw identifiers, it leaves the need for detecting unexpected sensitive content in S3 objects unmet.
D:A cryptographic hash maps inputs to fixed outputs without keeping an ordinary reversible mapping; it would target comparing known identifiers without storing plaintext values, while the question is about detecting unexpected sensitive content in S3 objects.
E:Aggregation can report measurements across groups while excluding direct person-level rows from published outputs; its benefit is publishing population statistics without individual record detail; that is different from detecting unexpected sensitive content in S3 objects.
Question 383
A fraud rule must compute each customer’s rolling five-minute transaction sum from a continuous stream, surviving processor restarts without losing aggregate state. Which approach fits?
- Idempotent output writes
- Kinesis retention adjustment
- Managed Service for Apache Flink keyed windows
- Stateless transformation
- Durable consumer checkpoints
Explanation
Correct Answer
C:Managed Service for Apache Flink can maintain keyed window aggregates with checkpoint-based state recovery across streaming records; in this scenario, use a keyed time window in Managed Service for Apache Flink and configure suitable checkpointing and event-time handling so state can recover.
Incorrect Answers
A:Idempotent writes make replaying the same logical input safe without duplicating downstream effects; its benefit is preventing duplicate target rows after event redelivery; that is different from running recoverable per-customer rolling-window totals in managed Flink.
B:Stream retention controls how long published records remain available for replay in Kinesis Data Streams; the current need is for running recoverable per-customer rolling-window totals in managed Flink, not extending the recovery window for an offline consumer.
D:Stateless processors derive each output solely from their current input and need no cross-event accumulated state; this helps with applying independent per-record normalization rules, not running recoverable per-customer rolling-window totals in managed Flink.
E:Checkpoints track a stream application's committed read position separately from the stream itself; although useful for resuming from the last successfully processed record, it leaves the need for running recoverable per-customer rolling-window totals in managed Flink unmet.
Question 384
A new RDS analytics source must meet encryption-at-rest rules for its tables and backups. What configuration fits?
- SSE-KMS on S3 objects
- EBS volume encryption
- RDS storage encryption
- KMS key policy permissions
- S3 Bucket Key with SSE-KMS
Explanation
Correct Answer
C:RDS storage encryption uses KMS integration to protect underlying database storage and supported related backups; in this scenario, enable storage encryption when creating the instance or cluster and plan migration for existing unencrypted resources as supported.
Incorrect Answers
A:SSE-KMS uses an AWS KMS key for server-side encryption of objects stored in S3; it would target enforcing controlled key usage for stored sensitive lake objects, while the question is about encrypting a managed relational source's stored data.
B:EBS encryption protects supported block volumes at rest and in transit between instance and volume; its benefit is protecting EC2-attached processing scratch volumes; that is different from encrypting a managed relational source's stored data.
D:Key policies define key-level permission foundations for KMS operations, alongside other applicable access policies; this can support allowing authorized ETL roles to decrypt with an existing customer-managed key, but would not address the need for encrypting a managed relational source's stored data.
E:S3 Bucket Keys can reduce the number of KMS requests made for eligible SSE-KMS object operations; this helps with reducing KMS request costs for many encrypted objects, not encrypting a managed relational source's stored data.
Question 385
An Athena query references valid tables but fails because its configured results bucket is inaccessible. What must be corrected?
- Athena workgroup controls
- Athena SQL editor
- Athena notebook Spark session
- Spark dataframe transformations
- Athena query-result S3 location
Explanation
Correct Answer
E:Athena SQL query results are written to an S3 output location subject to workgroup and permission settings; in this scenario, ensure the workgroup and calling principal can use the expected S3 result location and any applicable encryption settings.
Incorrect Answers
A:Athena workgroups provide query settings, usage controls and separation for groups of users; this helps with limiting scanned query cost for exploratory users, not troubleshooting a query that fails before returning rows.
B:Athena SQL editor runs interactive SQL queries over configured catalogs and workgroups; although useful for running ad-hoc SQL against Glue catalog tables, it leaves the need for troubleshooting a query that fails before returning rows unmet.
C:Athena notebooks can provide an interactive Apache Spark environment for data exploration; it would target exploring large datasets with Spark in an Athena-integrated notebook, while the question is about troubleshooting a query that fails before returning rows.
D:Spark DataFrames provide distributed operations such as filters, joins and aggregations within supported notebook sessions; its benefit is exploring joins on a distributed lake dataset; that is different from troubleshooting a query that fails before returning rows.
Question 386
A versioned evidence bucket needs an additional authorization check before permanent deletion of protected object versions. Which feature supplies it?
- DynamoDB TTL attribute
- S3 bucket versioning
- S3 MFA Delete
- DynamoDB point-in-time recovery
- S3 delete-marker recovery
Explanation
Correct Answer
C:MFA Delete adds an MFA requirement to certain versioning-related delete operations when configured by the root account; in this scenario, mFA Delete requires a valid MFA code for designated versioning and permanent-delete actions, with operational limitations understood.
Incorrect Answers
A:DynamoDB TTL uses a specified numeric epoch-seconds attribute to expire items asynchronously; it would target removing stale session records from DynamoDB, while the question is about adding strong protection to permanent deletion of object versions.
B:Versioning preserves separate revisions of an object key to aid recovery from overwrites and deletes; its benefit is recovering a previously overwritten object revision; that is different from adding strong protection to permanent deletion of object versions.
D:PITR supports continuous backups of a DynamoDB table within its supported recovery window; this can support restoring a table after accidental bulk writes, but would not address the need for adding strong protection to permanent deletion of object versions.
E:Deleting the current delete marker can reveal an older object version in a versioned bucket; this helps with restoring a logically deleted current object, not adding strong protection to permanent deletion of object versions.
Question 387
A central catalog team wants separate organizational boundaries for finance and sales governance. What structuring feature helps?
- SageMaker domain unit
- SageMaker Catalog business asset
- Glue secret reference
- SageMaker Unified Studio project
- Glue JDBC connection definition
Explanation
Correct Answer
A:Domain units can organize teams and governance boundaries within a SageMaker Unified Studio domain; in this scenario, define domain units and assign appropriate owners and policies instead of using a single unbounded project for all teams.
Incorrect Answers
B:SageMaker Catalog can provide business-oriented discovery and descriptions of governed data assets; this helps with helping analysts discover an approved business dataset, not delegating catalog administration to a business unit.
C:A Glue connection can use a secret for database credentials when configured and permitted; although useful for rotating shared source credentials without editing multiple jobs, it leaves the need for delegating catalog administration to a business unit unmet.
D:A Unified Studio project provides a collaborative workspace and governed resources for data and analytics activities; it would target organizing a data team's approved work context, while the question is about delegating catalog administration to a business unit.
E:A Glue connection saves reusable endpoint, authentication and networking information for supported sources; its benefit is reusing database connectivity settings across Glue jobs; that is different from delegating catalog administration to a business unit.
Question 388
A validation function needs to call one enrichment helper and return its small result before responding. What mechanism may suffice?
- AWS Step Functions state machine
- Glue workflow
- EventBridge rule
- Amazon MWAA DAG
- Lambda direct invocation
Explanation
Correct Answer
E:One Lambda function can synchronously or asynchronously invoke another for small, bounded tasks; in this scenario, invoke the helper with the appropriate mode and timeouts; a full workflow service is unnecessary for this small call chain.
Incorrect Answers
A:Step Functions coordinates service tasks with explicit states, branching, errors and retries; it would target orchestrating a serverless ETL with conditional paths, while the question is about initiating a single short helper action from code.
B:A Glue workflow links Glue triggers, crawlers and jobs into a managed ETL dependency sequence; its benefit is sequencing a Glue-only crawl and transform chain; that is different from initiating a single short helper action from code.
C:EventBridge matches emitted events and routes them to targets without tracking a multi-step workflow state; the current need is for initiating a single short helper action from code, not routing a completed-upload event to the next service.
D:Amazon MWAA provides managed Apache Airflow for dependency graphs expressed as DAGs; this can support running an established Airflow-based cross-platform DAG, but would not address the need for initiating a single short helper action from code.
Question 389
Only a few small JSON files arrive each week and each requires a two-second normalization. Which compute model minimizes standing capacity?
- Redshift Serverless
- Provisioned Redshift cluster
- Lambda short execution
- EMR persistent cluster
- Athena on-demand SQL
Explanation
Correct Answer
C:Lambda charges for invoked execution and suits bounded tasks under platform runtime constraints; in this scenario, use event-driven Lambda processing with sufficient memory and error handling, rather than running an always-on compute fleet.
Incorrect Answers
A:Redshift Serverless runs warehouse workloads without manually managing provisioned clusters; this can support running variable warehouse SQL workloads with less infrastructure management, but would not address the need for handling sporadic lightweight event transformations without idle servers.
B:Provisioned Redshift compute provides explicit sizing and reservations for more predictable warehouse workloads; this helps with optimizing sustained analytics demand under stable capacity, not handling sporadic lightweight event transformations without idle servers.
D:A persistent EMR cluster can run continuing workloads with custom node and framework configurations; it would target maintaining specialized continuously running Spark infrastructure, while the question is about handling sporadic lightweight event transformations without idle servers.
E:Athena can query data in S3 without administering a persistent warehouse cluster; its benefit is serving occasional lake SQL queries with variable demand; that is different from handling sporadic lightweight event transformations without idle servers.
Question 390
A thousand nightly independent jobs all start at midnight and overload the metadata database. Which scheduling option smooths launch peaks?
- Airflow task retry policy
- Step Functions execution history
- Airflow dependency trigger rule
- EventBridge Scheduler flexible time window
- Glue conditional trigger
Explanation
Correct Answer
D:Flexible time windows let a scheduled invocation occur within a configured interval instead of at an exact instant; in this scenario, allow a flexible invocation window for workloads without strict start-time requirements to distribute schedule pressure.
Incorrect Answers
A:Airflow tasks support retry counts and delays within a DAG's execution schedule; it would target retrying a transiently failing DAG task, while the question is about spreading noncritical batch launches to avoid thundering herds.
B:Step Functions maintains execution event history for supported workflows and helps locate failed states; its benefit is tracing the precise failure transition in a workflow; that is different from spreading noncritical batch launches to avoid thundering herds.
C:Airflow trigger rules determine when a downstream task may run relative to upstream task states; the current need is for spreading noncritical batch launches to avoid thundering herds, not ensuring a cleanup task runs after upstream failures.
E:Glue conditional triggers can start downstream jobs when designated upstream jobs or crawlers reach configured states; this helps with running a publish job only after upstream Glue success, not spreading noncritical batch launches to avoid thundering herds.