Explore AWS CodePipeline MCQ questions and answers focusing on advanced topics like custom actions, multi-region and cross-account pipelines, and handling manual approval processes. Perfect for enhancing knowledge about configuring CodePipeline efficiently, these questions are ideal for AWS certification aspirants and professionals working with CI/CD pipelines.
MCQs on Using Custom Actions in CodePipeline
What is the purpose of using custom actions in AWS CodePipeline? a) To enable parallel execution of pipelines b) To integrate third-party tools or custom logic into the pipeline c) To manage pipeline versioning automatically d) To provide automated rollback during deployment
How can a custom action be added to a CodePipeline? a) By creating a Lambda function and adding it to the pipeline b) By directly writing code into the pipeline console c) By using the AWS SDK to modify the pipeline JSON definition d) By integrating an EC2 instance with the pipeline
Which AWS service is commonly used to implement custom actions in CodePipeline? a) Amazon EC2 b) AWS Lambda c) Amazon RDS d) AWS Glue
What is a key requirement for implementing custom actions in a CodePipeline stage? a) Custom actions must run on dedicated hardware b) The custom action must have permissions defined in IAM c) Custom actions must use S3 as a data store d) Only Python scripts are supported for custom actions
How can custom actions in CodePipeline be monitored? a) Using CloudWatch Logs for detailed activity tracking b) Using AWS Trusted Advisor reports c) Monitoring through AWS Config rules d) Only through manual inspection of pipeline execution
Which AWS SDK is used for integrating custom actions into CodePipeline? a) AWS SDK for JavaScript b) AWS SDK for Python (Boto3) c) AWS SDK for Ruby d) AWS SDK for PHP
What is the purpose of the PollForJobs API in CodePipeline custom actions? a) To retrieve job details from CodePipeline for execution b) To submit jobs for approval in the pipeline c) To monitor the progress of a pipeline stage d) To automate rollback actions
MCQs on Multi-Region and Cross-Account Pipelines
Why would you use a multi-region pipeline in AWS CodePipeline? a) To reduce data transfer costs between AWS services b) To ensure high availability and redundancy across regions c) To automatically update pipeline versions in different regions d) To minimize IAM permissions configuration
What is required to configure cross-account pipelines in CodePipeline? a) VPC Peering between accounts b) IAM roles with appropriate permissions for each account c) Direct integration with AWS Organizations d) Deployment of resources only in the source account
How can artifacts be securely shared in a cross-account pipeline? a) Using an S3 bucket with cross-account permissions b) Encrypting artifacts with a custom encryption key c) Using EC2 instances for artifact transfer d) Deploying artifacts using AWS Systems Manager
Which service is commonly used to replicate CodePipeline actions across regions? a) AWS CodeDeploy b) Amazon S3 c) AWS CloudFormation StackSets d) AWS CodeBuild
What IAM policy must be applied for cross-account pipelines? a) Read-only access for the source account b) AssumeRole permissions for pipeline actions c) AdministratorAccess for all accounts d) FullAccess to all CodePipeline stages
In a multi-region pipeline, what determines the region where pipeline actions are executed? a) The region specified in the pipeline JSON definition b) The region of the source artifact c) The default region set in the AWS Management Console d) The region where the pipeline was first created
What AWS service can be used to deploy infrastructure across multiple regions in a pipeline? a) AWS CloudFormation b) AWS Glue c) AWS Trusted Advisor d) Amazon DynamoDB
MCQs on Handling Manual Approval Processes
What is the main use case for manual approval actions in CodePipeline? a) To validate changes before they are deployed to production b) To automatically approve changes based on metrics c) To trigger additional stages in a pipeline d) To enable rollback after deployment
How can manual approval actions be configured in CodePipeline? a) By adding an approval step in the pipeline stage definition b) By using AWS Config rules c) By creating a Lambda function for approvals d) By integrating with AWS Trusted Advisor
What permissions are required for users approving manual actions in CodePipeline? a) Read-only access to pipeline stages b) IAM policies granting access to approve actions c) Full administrative privileges in the AWS account d) EC2 instance profile permissions
Which notification service can be used with manual approval actions? a) Amazon SNS for email or SMS notifications b) AWS CloudTrail for logging approvals c) Amazon S3 for storing approval metadata d) AWS Trusted Advisor for policy recommendations
What happens if a manual approval action is not approved within the specified timeout? a) The pipeline execution is paused indefinitely b) The pipeline execution fails and moves to the next stage c) The pipeline automatically retries the approval action d) The pipeline execution is terminated
How can manual approval comments be recorded? a) By using the AWS Management Console or API b) By integrating with AWS Systems Manager c) By adding comments in CloudWatch Logs d) By configuring approval logging in S3
What is a key benefit of using manual approvals in CI/CD pipelines? a) Ensures better human oversight of critical changes b) Speeds up deployment to production c) Automates rollback in case of failure d) Reduces the need for automated tests
How can manual approval actions be automated in certain conditions? a) By integrating with AWS Lambda for automated decision-making b) By using predefined conditions in the CodePipeline JSON definition c) By setting the approval action timeout to zero d) By using IAM policies to bypass approvals
In a manual approval step, which metadata can be included in notifications? a) Pipeline name, stage name, and execution ID b) CloudWatch log details c) Artifact details and EC2 instance state d) CodeBuild logs
Which AWS service can be integrated to provide audit trails for manual approvals? a) AWS CloudTrail b) Amazon CloudWatch c) AWS Config d) AWS Trusted Advisor
What is the default status of a pipeline if a manual approval action is not approved? a) Failed b) Paused c) In Progress d) Succeeded
Answers
QNo
Answer (Option with Text)
1
b) To integrate third-party tools or custom logic into the pipeline
2
a) By creating a Lambda function and adding it to the pipeline
3
b) AWS Lambda
4
b) The custom action must have permissions defined in IAM
5
a) Using CloudWatch Logs for detailed activity tracking
6
b) AWS SDK for Python (Boto3)
7
a) To retrieve job details from CodePipeline for execution
8
b) To ensure high availability and redundancy across regions
9
b) IAM roles with appropriate permissions for each account
10
a) Using an S3 bucket with cross-account permissions
11
c) AWS CloudFormation StackSets
12
b) AssumeRole permissions for pipeline actions
13
a) The region specified in the pipeline JSON definition
14
a) AWS CloudFormation
15
a) To validate changes before they are deployed to production
16
a) By adding an approval step in the pipeline stage definition
17
b) IAM policies granting access to approve actions
18
a) Amazon SNS for email or SMS notifications
19
d) The pipeline execution is terminated
20
a) By using the AWS Management Console or API
21
a) Ensures better human oversight of critical changes
22
a) By integrating with AWS Lambda for automated decision-making