AWS DevOps I/O Configuration & Sensors 3

Question 1

An AWS CodePipeline action produces output artifacts that must be consumed by a downstream stage. Where are these artifacts stored by default?

Accepted Answer

Amazon S3 bucket managed by CodePipeline

Answer

CodePipeline stores input and output artifacts in an Amazon S3 bucket it manages, which acts as the shared I/O layer between pipeline stages.

Question 2

When configuring an AWS IoT rule to route sensor telemetry into a Lambda function, which component evaluates incoming MQTT messages to determine whether the rule fires?

Accepted Answer

IoT Rule SQL statement

Answer

The AWS IoT Rules Engine uses a SQL-like statement to filter and transform MQTT messages before routing them to the configured action target.

Question 3

A DevOps team wants CloudWatch to alert when a connected sensor stops publishing data for more than 5 minutes. Which CloudWatch feature handles this?

Accepted Answer

Missing Data treatment set to 'breaching'

Answer

Setting the missing data treatment to 'breaching' on a CloudWatch alarm causes it to transition to ALARM state when no data points arrive within the evaluation period.

Question 4

In a CodeBuild project, what is the correct buildspec field for specifying files that should be exported as output artifacts to S3?

Accepted Answer

artifacts: files:

Answer

The 'artifacts' block in buildspec.yml, specifically the 'files' key, lists the files or directories CodeBuild packages and uploads as output artifacts.

Question 5

An AWS IoT Greengrass core device needs to process sensor data locally without internet connectivity. Which Greengrass component type runs the custom processing logic at the edge?

Accepted Answer

Lambda function component

Answer

AWS IoT Greengrass supports Lambda function components that execute locally on the core device, enabling offline sensor data processing at the edge.

AWS Practice Test

AWS Practice Test

AWS DevOps I/O Configuration & Sensors 3