Practice Free DVA-C02 Exam Online Questions
A development team wants to build a continuous integration/continuous delivery (CI/CD) pipeline. The team is using AWS CodePipeline to automate the code build and deployment. The team wants to store the program code to prepare for the CI/CD pipeline.
Which AWS service should the team use to store the program code?
- A . AWS CodeDeploy
- B . AWS CodeArtifact
- C . AWS CodeCommit
- D . Amazon CodeGuru
C
Explanation:
AWS CodeCommit is a service that provides fully managed source control for hosting secure and scalable private Git repositories. The development team can use CodeCommit to store the program code and prepare for the CI/CD pipeline. CodeCommit integrates with other AWS services such as CodePipeline, CodeBuild, and CodeDeploy to automate the code build and deployment process.
Reference: [What Is AWS CodeCommit? – AWS CodeCommit]
[AWS CodePipeline – AWS CodeCommit]
A developer is creating an Amazon DynamoDB table by using the AWS CLI. The DynamoDB table must use server-side encryption with an AWS owned encryption key
How should the developer create the DynamoDB table to meet these requirements?
- A . Create an AWS Key Management Service (AWS KMS) customer managed key. Provide the key’s Amazon Resource Name (ARN) in the KMSMasterKeyld parameter during creation of the DynamoDB table
- B . Create an AWS Key Management Service (AWS KMS) AWS managed key Provide the key’s Amazon Resource Name (ARN) in the KMSMasterKeyld parameter during creation of the DynamoDB table
- C . Create an AWS owned key Provide the key’s Amazon Resource Name (ARN) in the KMSMasterKeyld parameter during creation of the DynamoDB table.
- D . Create the DynamoDB table with the default encryption options
D
Explanation:
Default SSE in DynamoDB: DynamoDB tables are encrypted at rest by default using an AWS owned key (SSE-S3).
No Additional Action Needed: Creating a table without explicitly specifying a KMS key will use this default encryption.
Reference: DynamoDB Server-Side
Encryption: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Encryption
A company is running a custom application on a set of on-premises Linux servers that are accessed using Amazon API Gateway. AWS X-Ray tracing has been enabled on the API test stage.
How can a developer enable X-Ray tracing on the on-premises servers with the LEAST amount of configuration?
- A . Install and run the X-Ray SDK on the on-premises servers to capture and relay the data to the X-Ray service.
- B . Install and run the X-Ray daemon on the on-premises servers to capture and relay the data to the X-Ray service.
- C . Capture incoming requests on-premises and configure an AWS Lambda function to pull, process, and relay relevant data to X-Ray using the PutTraceSegments API call.
- D . Capture incoming requests on-premises and configure an AWS Lambda function to pull, process, and relay relevant data to X-Ray using the PutTelemetryRecords API call.
B
Explanation:
The X-Ray daemon is a software that collects trace data from the X-Ray SDK and relays it to the X-Ray service. The X-Ray daemon can run on any platform that supports Go, including Linux, Windows, and macOS. The developer can install and run the X-Ray daemon on the on-premises servers to capture and relay the data to the X-Ray service with minimal configuration. The X-Ray SDK is used to instrument the application code, not to capture and relay data. The Lambda function solutions are more complex and require additional configuration.
Reference: [AWS X-Ray concepts – AWS X-Ray]
[Setting up AWS X-Ray – AWS X-Ray]