AWS DevOps I/O Configuration & Sensors 4 — Questions and Answers
Question 1: A CodePipeline stage has two parallel actions, A and B. Action C in the next stage depends on output from both. How does CodePipeline handle this dependency?
- Action C runs only after Action A by default, ignoring Action B
- Action C must be configured with a manual approval to wait
- Action C must poll S3 until both artifact ZIPs appear
- Action C automatically receives combined artifacts once both actions complete (Correct answer)
Correct answer: Action C automatically receives combined artifacts once both actions complete
CodePipeline stages act as barriers — all parallel actions in a stage must succeed before the next stage starts, and all their artifacts are forwarded automatically.
Question 2: Which AWS service provides a managed MQTT broker endpoint that IoT devices use to publish and subscribe to sensor topics without managing broker infrastructure?
- AWS IoT Core (Correct answer)
- Amazon MQ
- Amazon MSK
- AWS IoT Events
Correct answer: AWS IoT Core
AWS IoT Core provides a fully managed MQTT message broker that scales automatically, eliminating the need to provision or manage broker infrastructure.
Question 3: A DevOps pipeline needs to inject a database connection string from AWS Secrets Manager into a containerized application at deploy time without baking secrets into the image. Which ECS task definition feature enables this?
- environment field with plaintext value
- secrets field referencing the Secrets Manager ARN (Correct answer)
- logConfiguration with awslogs driver
- healthCheck command with curl
Correct answer: secrets field referencing the Secrets Manager ARN
The ECS task definition 'secrets' field accepts a Secrets Manager ARN and injects the secret value as an environment variable at container startup.
Question 4: When AWS IoT Device Shadow is used for sensor configuration, what happens when a device reconnects and its reported state differs from the desired state?
- The device shadow is deleted and recreated
- An SNS notification is sent to the operator
- IoT Core sends a delta document to the device indicating the difference (Correct answer)
- The device must re-register before receiving configuration
Correct answer: IoT Core sends a delta document to the device indicating the difference
AWS IoT Device Shadow publishes a delta document on the shadow/update/delta topic whenever the reported and desired states diverge, prompting the device to reconcile.
Question 5: In AWS CodeDeploy, which lifecycle event hook is the best place to run smoke tests that validate I/O handling before traffic is shifted to the new deployment?
- BeforeInstall
- AfterAllowTestTraffic (Correct answer)
- ApplicationStop
- DownloadBundle
Correct answer: AfterAllowTestTraffic
AfterAllowTestTraffic fires after test traffic is routed to the new deployment, making it ideal for I/O smoke tests before shifting production traffic.
Question 6: A team streams sensor readings into Amazon Kinesis Data Streams. What is the maximum data retention period supported?
- 7 days
- 30 days
- 365 days (Correct answer)
- 24 hours
Correct answer: 365 days
Kinesis Data Streams supports extended data retention of up to 365 days, allowing replay of historical sensor data for debugging or reprocessing.
Question 7: Which CloudWatch metric namespace should a DevOps engineer query to view ReadIOPS and WriteIOPS metrics for an Amazon RDS instance?
- CWAgent/RDS
- AWS/EC2
- AWS/DatabaseInsights
- AWS/RDS (Correct answer)
Correct answer: AWS/RDS
RDS automatically publishes metrics such as ReadIOPS, WriteIOPS, and NetworkThroughput under the AWS/RDS namespace in CloudWatch.
AWS DevOps I/O Configuration & Sensors 4
A CodePipeline stage has two parallel actions, A and B.
Action C in the next stage depends on output from both.
How does CodePipeline handle this dependency?