1.

TELL ABT URSELF

2. TEL ABT UR PROJECT WHICH U VE WORKED?? 2 YEARS

AWS:

1. WHAT ARE THE TYPES OF EC2 MODEL ?

Ans : Amazon Elastic Compute Cloud (EC2) offers a wide range of instance types to
suit different workloads and use cases. Here are some of the EC2 instance types:

General Purpose Instances: These instances provide a balance of compute, memory,

and networking resources and are suitable for a wide range of applications.
Examples include the M6g, M5, T4g, T3, and A1 instances.

Compute-Optimized Instances: These instances are designed for high-performance

computing and are ideal for compute-intensive workloads such as data analytics,
high-performance computing, and machine learning. Examples include the C6g, C5,
C5n, and P3 instances.

Memory-Optimized Instances: These instances are designed for memory-intensive

workloads such as in-memory databases, real-time big data processing, and high-
performance computing. Examples include the R6g, R5, R5b, X1, and z1d instances.

Storage-Optimized Instances: These instances are optimized for high-performance

storage and are ideal for data warehousing, big data processing, and log
processing. Examples include the I3, D3, and H1 instances.

GPU Instances: These instances are optimized for graphics-intensive workloads such
as gaming, digital media, and machine learning. Examples include the G4, P3, and
Inf1 instances.

FPGA Instances: These instances are optimized for custom hardware acceleration
using field-programmable gate arrays (FPGAs). Examples include the F1 instances.

Arm-Based Instances: These instances use Arm-based processors and are optimized for
performance and cost-efficiency. Examples include the A1 and C6g instances.

Each instance type comes with different combinations of CPU, memory, storage,
network capacity, and pricing, so it is important to choose the right instance type
based on the specific requirements of your workload

2. WHAT TYPE OF EC2 INSTANCE U VE USED IN UR PROJECT

3. SNAPSHOT VS VOLUME

ANS : In Amazon Web Services (AWS), a snapshot and a volume are both types of
storage resources that can be used with Elastic Compute Cloud (EC2) instances.

A volume is a block storage device that can be attached to an EC2 instance. It

provides persistent storage for data, and can be used as the root device or
additional data storage. A volume is essentially a virtual hard disk that can be
created, attached, detached, and deleted as needed. Volumes can be created from
scratch, or from a snapshot.

A snapshot is a point-in-time copy of a volume. It captures the contents of the

volume at the time the snapshot was taken, and creates a new Amazon Elastic Block
Store (EBS) volume from that data. Snapshots are stored separately from the
original volume, and are used for backup, disaster recovery, or to create new
volumes. Snapshots can be created manually, or automatically using a backup policy.
Snapshots are incremental, meaning that only the changes made since the last
snapshot are saved, which helps to save time and storage space.

To summarize, a volume is a storage device that can be attached to an EC2 instance,

while a snapshot is a point-in-time copy of a volume that can be used to create new
volumes or for backup purposes. In general, volumes are used for persistent storage
and data access during the lifetime of an EC2 instance, while snapshots are used
for data backup and disaster recovery2.snap and volume

4. WHAT AND ALL INFO PRESENT IN UR BASIC AMI?

5. HOW TO MOVE AMI FROM ONE REGION TO ANOTHER REGION ??

ANS : To move an AMI (Amazon Machine Image) from one region to another, you can
follow these steps:Launch an EC2 instance in the source region using the AMI you
want to move.Stop the instance to ensure that the root device volume is in a
consistent state.Create a snapshot of the root device volume.Copy the snapshot to
the destination region using the AWS Management Console, CLI, or SDK.Create a new
AMI in the destination region using the copied snapshot.Optionally, launch a new
EC2 instance in the destination region to ensure that the new AMI is working
correctly.Here is a more detailed breakdown of these steps:Launch an EC2 instance
in the source region: You can launch an EC2 instance in the source region and
choose the AMI you want to move as the instance's boot device.Stop the instance:
After the instance is launched, stop it to ensure that the root device volume is in
a consistent state.Create a snapshot of the root device volume: With the instance
stopped, create a snapshot of the root device volume.Copy the snapshot to the
destination region: Use the AWS Management Console, CLI, or SDK to copy the
snapshot to the destination region. You can use the "Copy Snapshot" feature in the
EC2 console to copy the snapshot.Create a new AMI in the destination region: After
the snapshot has been copied, create a new AMI in the destination region using the
copied snapshot as the root device volume.Launch a new EC2 instance in the
destination region (optional): Launch a new EC2 instance in the destination region
using the new AMI to ensure that it is working correctly.It's important to note
that copying an AMI across regions incurs data transfer costs, so you should be
aware of any associated charges before proceeding with this process.

6. HOW TO INCREASE VOLUME SIZE?

ANS : To increase the size of an Amazon EBS (Elastic Block Store) volume attached
to an EC2 instance, you can follow these steps:
1. Identify the volume: First, you need to identify the EBS volume that you want to
resize. You can do this by looking at the volumes attached to your instance using
the EC2 console or the CLI.
2. Stop the instance: Before you can modify the size of the volume, you must first
stop the EC2 instance to which the volume is attached. You can do this using the
EC2 console or the CLI.
3. Modify the volume: Once the instance is stopped, you can modify the size of the
volume using the EC2 console or the CLI. In the EC2 console, you can right-click on
the volume and choose "Modify Volume" to open the modify volume wizard. In the
wizard, you can specify the new size for the volume.
4. Start the instance: After you have modified the volume, start the EC2 instance.
The new size of the volume will be reflected in the operating system of the
instance.
5. Extend the file system: If you want to use the additional space, you will need
to extend the file system on the volume. The exact steps to do this will depend on
the operating system you are using.
It's important to note that increasing the size of an EBS volume may result in
downtime for your instance while it is stopped. Additionally, there may be
additional charges associated with increasing the size of an EBS volume, so you
should be aware of any associated costs before proceeding with this process.

ELB:

1. WHAT ARE THE DIFFERENT TYPES OF ELB??

2. IN WHICH SCENARION YOU WILL USE OR DECIDE UR ELB TYPES?

3. ELB AND ITS LAYERS?

4. LIFECYCLE HOOK POLICY IN ELB?

5. IF ANY ISSUES IN ELB, WHERE YOU WILL GO AND CHECK ??

6. WHAT IS DIFF BW HEALTH CHECKS IN ELB ....EC2 VS ELB??

7. AUTOSCALING POLICY

ROUTE 53:

1. WHAT ARE THE RECORDS SET AVAILABLE IN R53 AND FOR WT PURPOSE ULL CHOOSE THE
RECORD TYPE

2. WHAT ARE THE TYPES OF ROUTING POLICY AVAILABLE IN ROUTE 53?

3. WHAT IS DIFF BETWEEN A VS CNAME RECORD

IAM:

1. ROLE VS POLICY

2. HOW ULL MAINTAIN ACCESS KEY AND SECRET KEY

3. WHAT IS INLINE POLICY IN IAM

4. IAM CROSS ACCOUNT AUTHENTICATION ?

S3:

1. S3 POLICY

2. S3 --- CROSS REGION REPLICATION

VPC:

1. VPC PEERING?

2. ROUTING POLICY

3. CIDR RANGE

4. PUBLIC SUBNET VS PRIVATE SUBNET

5. VPC ENDPOINT ---USE

6. TYPES OF IP AND WHAT TYPE OF IP RANGE WE ARE USING

7. NACL VS SG

8. VPC peering vs vpc transit gateway AND ITS ADVANTAGE

RDS:

1. AMAZON AURORA AND ADVANTAGE

2. HOW YOU WILL MAINTAIN BACKUP OF RDS

3. SUPPOSE UR DB ENDPOINT IS DOWN, HOW YOU WILL TROUBLESHOOT

4. HOW YOU WILL GIVE ACCESS TO DATABASE ?

CLOUDFORMATION:

1. WHAT ARE THE RESOURCES U CREATED USING CFT

2. WRITE ONE SAMPLE CFT TEMPLATE WHICH U VE CREATED

GENERAL QNS:

1. WHAT ARE THE SERVICES AVAILABLE IN AWS WHICH IS NOT REGION SPECIFIC

2. CLOUDWATCH VS CLOUDTRIAL

3. WHAT IS BLUE GREEN DEPLOYMENT? OR WHAT TYPE OF DEPLOYMENT STRATEGY UR USING IN

UR PROJECT??

DEVOPS:

1. WHAT IS THE BRANCHING STRATEGY UR USING IN UR PROJECT?

ANS: Git Flow is the most widely known branching strategy that takes a multi-
branch approach to manage the source code.
This approach consists of two main branches that live throughout the
development lifecycle.
Dev,QA, feature, release, and hotfix and finel code merge remote repository.

2. GIT PULL VS GIT FETCH

ANS : Git Fetch is the command that tells the local repository that there are
changes available in the remote repository without bringing the changes into the
local repository.
Git Pull on the other hand brings the copy of the remote directory changes
into the local repository.

3. GIT STASH?
ANS :GIT stash takes the current state of the working directory and index and puts
in on the stack for later and gives you back a clean working directory.
So in case if you are in the middle of something and need to jump over to the
other job,
and at the same time you don’t want to lose your current edits then you can use
GIT stash.
4. SUPPOSE IF UR DEPLOYMENT IS FAILED,HOW YOU WILL REVERT UR CHANGES?
ANS : If you've already committed/pushed, use $git revert. If you haven't committed
yet,
and are working on your own branch all by yourself, you can go ahead and do $git
reset.
This simply wipes out all your as-yet uncommitted changes and deposits you back on
the doorstep of your most recent commit.

5. HOW YOU WILL RESOLVE GIT MERGE CONFLICT

6. Git tag
ANS : Tags are ref's that point to specific points in Git history.
Tagging is generally used to capture a point in history that is used for a
marked version release (i.e. v1. 0.1).
A tag is like a branch that doesn't change. Unlike branches, tags, after
being created, have no further history of commits.
7. Git pull vs git fetch vs git clone.

8. What s pull request

ANS : Pull requests let you tell others about changes you've pushed to a branch in
a repository on GitHub.
Once a pull request is opened, you can discuss and review the potential
changes with collaborators and add follow-up commits before your changes are merged
into the base branch.
9. How will you confirm that you have updated code in u r local?
ANS: Inspecting Local Changes.

Without further options, "git diff" will show us all current local changes in
our working copy that are unstaged.
If you want to see only changes that have already been added to the Staging
Area, "git diff --staged" is your command of choice.

10. How will decide which code shd be moved to production if conflict occurs
11.. Git vs SVN?
ANS: Git has a Distributed Model. SVN has a Centralized Model. In git every user
has their own copy of code on their local like their own branch.
In SVN there is central repository has working copy that also make changes and
committed in central repository.

12. What is distributed versions control system?

ANS: A distributed version control system (DVCS)
brings a local copy of the complete repository to every team member's
computer,
so they can commit, branch, and merge locally.

13.How will you know in GIT if a branch has been already merged into master?
ANS: To know if a branch is already merged into the master, first, open the Git
repository and try to merge the branch.
As a result, either the “Already up to date” message will appear, which means
the branch is already merged into the master.

14. Git rebase VS git merge?

ANS: In the process, rebase flattens the history, removing unwanted entries.
Git merge, on the other hand, only changes the target branch and creates a commit,
preserving the history of the source branch.

15. Git status vs git diff?

ANS : While git status only tells you the state of your file changes, git diff
tells you the exact changes.
You can use git diff to compare your changes before staging or committing
them.

16. How to fix broken commit?

ANS : In order to fix broken commit, We can the command " git commit --amend".
When you run this commend, you can fix the commit msg in the editor.

17. Feature branching in GIT?

ANS : The core idea behind the Feature Branch Workflow is that
all feature development should take place in a dedicated branch instead of the
main branch.

18. You accidentally committed on the "master" branch instead of "feature/login".

Describe the process of correcting this mistake
ANS: First, you should check out the "feature/login" branch.
There, copy the desired commit over using the git cherry-pick command.
19. How can you undo a commit that has already been pushed to a shared branch on a
remote repository?
20. You have accidentally deleted a branch. Is there any way to recover it and
bring it back?
21. what is git cherry pick?
ANS:git cherry-pick is a powerful command that enables arbitrary Git commits to be
picked by reference and appended to the current working HEAD.
Cherry picking is the act of picking a commit from a branch and applying it to
another. git cherry-pick can be useful for undoing changes.

DOCKER INTERVIEW QNS:

1. Docker file we give expose and we give -p option while running docker. What is
difference?
2. Docker container and VM - What is difference?
3. Why should I go for docker in my project
ANS: Docker enables faster software delivery cycles.
Docker containers make it easy to put new versions of software,
with new business features, into production quickly—and to quickly roll back
to a previous version if you need to.

4. docker architecture?
ANS: Docker architecture. Docker uses a client-server architecture.
The Docker client talks to the Docker daemon, which does the heavy lifting of
building, running, and distributing your Docker containers.
The Docker client and daemon can run on the same system, or you can connect a
Docker client to a remote Docker daemon.

5. docker kill, docker pause and docker stops

6. CMD and Entry point - What is difference----
AND : CMD - The CMD describes the default container parameters or commands. The
user can easily override the default command when you use this.
ENTRYPOINT - A container with an ENTRYPOINT is preferred when you want to
define an executable.
You can only override it if you use the --entrypoint flag.

7. What is difference between copy and add in docker file

8. Difference between ENV and ARG in docker file.

ANS: 1.ARG- argument are only available during the bulild of a docker image.
 ENV- while env variables are available to both image and container.
2.ARG- values are not accessible to running containers, ARG values not
available once the image is built.
ENV- values can be accessed at th build time as well as at the running of
the container
Example: ARG values include library version, Ubuntu version etc..
ENV values aer API keys,database URLs, secret keys etc..

9. What is difference between run and cmd

10. Why should i go for docker volume?

ANS:Docker containers are used to run applications in an isolated environment.
By default, all the changes inside the container are lost when the container
stops.
If we want to keep data between runs, Docker volumes and bind mounts can help.

11. How to share docker data in multiple containers

12. Do you have experience in writing docker file?
13. Where will you push your docker image
14. Docker attach
15. How will u push docker image in docker hub
16. How to add volumes to running container
17. Can I limit the file size/CPU ultization for a docker in my machine
18. Docker network difference/advantage - host, bridge and none
19. Best practices for writing docker file
20. How to communicate between 2 containers in different network.
21. what is docker link and its advantages
22. docker link vs depends_on
23. what is virtualisation
24. what is microservices
25. what is difference bw -v and mount
26. how to remove only stopped containers
27. what is docker swarm
orchestration
kubernetes
dockerswarm
mesos
28. difference between docker swarm vs kubernetes
29 .what is the orchestration container
30. what is kubernetes
31. how to tune ur docker file
32. Multi stage builds in docker
33. how you will confirm there is no security vulnerability in public image
34. how to monitor docker container
35. how u ll handle/store ur private image in your env
36. how to set resource limit for ur container
37.what is difference between bridge network and custom bridge network?

jenkins:

1. how ull configure master-slave in jenkins

2. what plugins u ve used in ur project

3. how you will take backup of ur jenkins configuration

4. downstream and upstream in jenkins

5. how you will give access to ur jenkins pipeline

6. how you will notify to the developers if pipeline is stopped or any errors

7. what is difference bw scripted vs declarative pipeline

terraform:

1. terraform backend

2. terraform provisioners

3. terraform providers

4. how ull maintain the code of different environment in terraform

5. terraform state file

6. terraform state file ---how you will maintain

7. scenario qns

8. how you will lock ur statefile

ansible:

1. what type of mechanism ansible is following

2. what and all modules u ve used in ur project

3. ansible handlers and its purpose

4. ansible template module

5. ansible roles ?

6. ansible galaxy and its purpose

7. one sample yaml file

8. one playbook need to be executed in one particular machine

9. one modules in the playbook need to be excuted in one particular machine

10. loop module