Wipro AWS Cloud Support L2 Interview Experience: 32 Questions With Complete Practical Answers
Wipro AWS Cloud Support L2 Interview Experience: 32 Questions With Complete Practical Answers
AWS, EC2, EBS, Networking, S3, Linux, Databases, Kubernetes, Terraform, and Troubleshooting
A friend recently attended a Wipro AWS Cloud Support L2 interview. The interview was hands-on and scenario-heavy, with very little textbook theory.
The questions covered AWS infrastructure, Linux administration, networking, databases, containers, Infrastructure as Code, monitoring, and web servers.
This is what makes an L2 Cloud Support interview different from a basic technical screening.
Knowing what a Security Group is will not be enough if the interviewer asks why an application remains unreachable even when port 443 is open.
Knowing what EBS is will not be enough if you cannot explain how to attach a volume, create a filesystem, mount it, and configure persistent mounting on Linux.
The interviewer wants to understand how you investigate problems, use commands, identify root causes, and explain your decisions.
This guide covers all 32 questions using eight attributes:
Simple Concept
Why We Need It
How It Works
Production Example
Command / Configuration
Common Interview Trap
Candidate-Style Answer
Memory Trick
Note: These are preparation notes based on a friend’s reported interview experience, not an official Wipro question paper.
Section 1: Introduction and Experience
Q1. Tell me about yourself.
1. Simple Concept
Your introduction is a short summary of your professional background, technical skills, responsibilities, and career direction.
2. Why We Need It
The interviewer uses your introduction to understand whether your experience matches the AWS Cloud Support L2 role.
3. How It Works
Structure your introduction around your experience, core technologies, operational responsibilities, one practical example, and why the role interests you.
4. Production Example
You might describe troubleshooting EC2 instances, investigating Linux performance problems, configuring IAM permissions, monitoring AWS resources, or supporting application deployments.
5. Command / Configuration
There is no specific command for an introduction. Prepare one genuine technical example and explain your investigation process.
6. Common Interview Trap
Listing 15 tools without explaining what you have actually done with them. The interviewer may immediately ask you to troubleshoot something using one of those tools.
7. Candidate-Style Answer
“I am a cloud and DevOps professional with experience in cloud infrastructure, Linux administration, automation, monitoring, and troubleshooting. My technical knowledge includes AWS services such as EC2, EBS, S3, IAM, VPC, and CloudWatch, along with Linux, networking, containers, and Infrastructure as Code.
My approach to technical issues is to understand the symptoms, collect evidence, investigate the affected components, identify the root cause, and validate the resolution. I am interested in this AWS Cloud Support L2 opportunity because it involves cloud operations, infrastructure troubleshooting, and improving service reliability.”
Customize this answer to your actual experience. Do not claim production experience you do not have.
8. Memory Trick
Remember: Experience → Skills → Responsibilities → Example → Career Goal.
Q2. Explain your roles, responsibilities, and day-to-day activities.
1. Simple Concept
Responsibilities describe the operational and technical tasks you perform in your job.
2. Why We Need It
The interviewer wants to know whether you understand real operational work, incident handling, and infrastructure management.
3. How It Works
Explain your regular activities, monitoring process, troubleshooting responsibilities, automation work, and incident documentation.
4. Production Example
An application becomes slow. You check CloudWatch metrics, Linux resource usage, application logs, network connectivity, and recent changes before deciding on the next action.
5. Command / Configuration
uptime
free -h
df -h
top
systemctl --failed
journalctl -p err -bThese commands help investigate system load, memory, disk capacity, failed services, and system errors.
6. Common Interview Trap
Saying only, “I monitor servers and resolve tickets.” Explain how you investigate, prioritize, communicate, and validate fixes.
7. Candidate-Style Answer
“My day-to-day activities include monitoring infrastructure, investigating alerts, troubleshooting Linux and cloud issues, supporting deployments, reviewing logs, managing incidents, and documenting resolutions. I prioritize issues based on impact and urgency, collect evidence before making changes, and verify system health after applying a fix.”
8. Memory Trick
Remember: Monitor → Investigate → Resolve → Validate → Document.
Q3. Which technology stack and Linux distributions have you worked with?
1. Simple Concept
Your technology stack is the collection of tools, platforms, operating systems, and services you use to perform your work.
2. Why We Need It
The interviewer wants to assess whether your experience matches the environment you will support.
3. How It Works
Explain each technology in terms of its purpose and how you have used it. For Linux, know the differences between distributions, package managers, service management, and logs.
4. Production Example
An application runs on Amazon Linux, but a troubleshooting script was written for Ubuntu. Package installation commands and some configuration paths may differ.
5. Command / Configuration
cat /etc/os-release
uname -r
which python3
systemctl status sshdPackage manager examples:
Ubuntu/Debian:
aptAmazon Linux 2023:
dnfRHEL-family systems:
dnforyum, depending on version
6. Common Interview Trap
Assuming all Linux distributions use the same package manager or service names. Ubuntu commonly uses apache2, while Amazon Linux commonly uses httpd.
7. Candidate-Style Answer
“I have worked with or studied technologies across cloud infrastructure, Linux administration, networking, containers, CI/CD, and Infrastructure as Code. My Linux troubleshooting process includes checking OS information, system resources, services, logs, permissions, and network connectivity. I would describe my experience with each tool according to the tasks I have actually performed.”
8. Memory Trick
Remember: Tool → Purpose → Practical Usage → Troubleshooting Example.
Section 2: EC2 and EBS
Q4. What are EC2 status checks?
1. Simple Concept
EC2 status checks help identify problems affecting an instance or its underlying AWS infrastructure.
2. Why We Need It
They help determine whether an instance is healthy and whether an infrastructure-level or instance-level problem requires investigation.
3. How It Works
System status checks identify problems involving the underlying AWS infrastructure.
Instance status checks identify problems involving the instance’s operating system, network configuration, or other instance-level conditions.
Attached EBS status checks can identify relevant storage connectivity or performance issues.
4. Production Example
An EC2 instance fails its instance status check after a boot problem. You investigate system logs, resource exhaustion, filesystem issues, and network configuration. If a system check fails, you also investigate AWS infrastructure health and available recovery options.
5. Command / Configuration
aws ec2 describe-instance-status \
--instance-ids i-xxxxxxxxxxxxxxxxx \
--include-all-instances6. Common Interview Trap
Assuming every failed check means you should immediately reboot the instance. First identify the type of failure and assess the impact of recovery actions.
7. Candidate-Style Answer
“EC2 provides system and instance status checks. System checks focus on the underlying AWS infrastructure, while instance checks focus on the instance itself. I would identify which check failed, review system and application logs, examine resource and networking issues, and choose an appropriate recovery action.”
8. Memory Trick
System = AWS infrastructure. Instance = guest operating environment.
Q5. Explain root EBS volumes, secondary volumes, and IOPS.
1. Simple Concept
Amazon EBS provides persistent block storage for EC2 instances.
A root volume normally contains the operating system, while secondary volumes can store application files, logs, or database data. IOPS means input/output operations per second.
2. Why We Need It
Different workloads have different storage requirements. Separating operating system and application data can simplify capacity management, backup planning, and performance troubleshooting.
3. How It Works
EBS volumes attach to EC2 instances and appear as block devices in the operating system. The filesystem must be configured before ordinary file operations can use a new volume.
Performance depends on volume type, capacity, provisioned IOPS where supported, throughput, and instance limits.
4. Production Example
A database server experiences slow queries. You investigate disk latency and IOPS utilization to determine whether storage performance is contributing to the problem.
5. Command / Configuration
lsblk
df -hT
iostat -xz 1These commands help inspect block devices, mounted filesystems, and storage performance. iostat may require the sysstat package.
6. Common Interview Trap
Confusing IOPS with throughput. IOPS measures operations per second; throughput measures the amount of data transferred per unit of time.
7. Candidate-Style Answer
“The root EBS volume generally stores the operating system, while secondary volumes store application or database data. IOPS measures the number of storage operations per second. I would select the volume type according to workload requirements and monitor latency, throughput, and IOPS when troubleshooting storage problems.”
8. Memory Trick
Root = OS. Secondary = data. IOPS = operations per second.
Q6. How do you change an EC2 instance type?
1. Simple Concept
Changing an EC2 instance type changes its available compute, memory, networking, or other instance capabilities.
2. Why We Need It
An application may need additional memory, more CPU capacity, or a different architecture as its workload changes.
3. How It Works
Check compatibility and capacity, plan downtime or a replacement strategy, stop the instance when required, modify its type, start it, and verify health.
4. Production Example
A workload repeatedly experiences memory pressure on a small instance. After reviewing metrics, you select a compatible instance with more memory and schedule the change.
5. Command / Configuration
aws ec2 stop-instances \
--instance-ids i-xxxxxxxxxxxxxxxxx
aws ec2 modify-instance-attribute \
--instance-id i-xxxxxxxxxxxxxxxxx \
--instance-type '{"Value":"m7i.large"}'
aws ec2 start-instances \
--instance-ids i-xxxxxxxxxxxxxxxxxUse the instance ID and type appropriate to your environment. Confirm the change is supported before executing it.
6. Common Interview Trap
Forgetting that stopping an instance can interrupt service and may change its public IPv4 address if it uses an automatically assigned address. Persistent storage, architecture compatibility, and instance availability also matter.
7. Candidate-Style Answer
“I would first review CPU, memory, and networking metrics to determine the required instance type. I would verify compatibility, plan the downtime or migration, stop the instance if necessary, modify its type, start it, and validate status checks and application health.”
8. Memory Trick
Assess → Plan → Stop → Modify → Start → Validate.
Q7. How do you attach and use multiple EBS volumes at the OS level?
1. Simple Concept
Attaching an EBS volume connects cloud storage to an EC2 instance. The operating system must recognize and configure the device before applications can use it.
2. Why We Need It
Applications often require separate storage for databases, logs, application files, or backups.
3. How It Works
Attach the volume in AWS, identify the device in Linux, create a filesystem if needed, mount it, and configure persistent mounting.
4. Production Example
A database server needs additional space. You attach a new volume, configure a filesystem, mount it at /data, and verify that the database can access the directory.
5. Command / Configuration
Identify the device:
lsblk
sudo fdisk -lCreate a filesystem only on a confirmed new or intentionally reformatted volume:
sudo mkfs.xfs /dev/nvme1n1Mount it:
sudo mkdir -p /data
sudo mount /dev/nvme1n1 /data
df -hTFor persistent mounting, retrieve the UUID:
sudo blkid /dev/nvme1n1Add the correct UUID and filesystem type to /etc/fstab, then test:
sudo mount -a6. Common Interview Trap
Running mkfs on a device that contains existing data. Formatting can destroy data. Also, AWS device names and Linux NVMe device names may differ.
7. Candidate-Style Answer
“I would attach the volume to the instance, identify it using lsblk, verify that it contains no data I need to preserve, create the appropriate filesystem, mount it, and configure UUID-based mounting in /etc/fstab. Finally, I would test the mount and validate ownership and permissions.”
8. Memory Trick
Attach → Identify → Format if needed → Mount → Persist → Verify.
Q8. How many EC2 instances can connect to a single EBS volume?
1. Simple Concept
Most EBS volumes are attached to one EC2 instance at a time, but eligible Provisioned IOPS SSD volumes support Multi-Attach.
2. Why We Need It
Some clustered applications require shared block-device access, although shared access introduces coordination and filesystem-safety requirements.
3. How It Works
EBS Multi-Attach supports eligible io1 and io2 volumes on supported Nitro-based instances within the same Availability Zone. Supported configurations allow up to 16 instances.
4. Production Example
A clustered application may need several instances to access a shared block device. The application and filesystem must coordinate concurrent writes safely.
5. Command / Configuration
Inspect volume attachments:
aws ec2 describe-volumes \
--volume-ids vol-xxxxxxxxxxxxxxxxx6. Common Interview Trap
Assuming Multi-Attach automatically makes a normal filesystem safe for simultaneous writes. It does not. The workload must support the shared-access model.
7. Candidate-Style Answer
“An ordinary EBS volume is generally attached to one instance. Eligible io1 and io2 volumes support Multi-Attach for up to 16 supported instances within the same Availability Zone. I would verify the volume and instance requirements and ensure the application and filesystem support coordinated concurrent access.”
8. Memory Trick
Ordinary EBS = single attachment. Eligible Multi-Attach = shared block access with coordination.
Q9. What is the difference between C-family and R-family instances?
1. Simple Concept
C-family instances are optimized for compute-intensive workloads, while R-family instances are optimized for memory-intensive workloads.
2. Why We Need It
Selecting the correct instance family improves workload performance and helps control infrastructure costs.
3. How It Works
Compute-optimized instances provide a high ratio of CPU capacity to memory. Memory-optimized instances provide more memory relative to CPU capacity.
4. Production Example
A CPU-heavy processing service may benefit from a C-family instance. An in-memory database may benefit from an R-family instance.
5. Command / Configuration
Inspect instance information:
aws ec2 describe-instances \
--instance-ids i-xxxxxxxxxxxxxxxxx \
--query 'Reservations[].Instances[].InstanceType'6. Common Interview Trap
Choosing an instance based on family name alone without measuring workload requirements. CPU, memory, network performance, and cost all matter.
7. Candidate-Style Answer
“C-family instances are designed for compute-intensive workloads such as batch processing, while R-family instances are suited to memory-intensive workloads such as in-memory databases. I would use monitoring data and workload benchmarks to choose the appropriate family.”
8. Memory Trick
C = Compute. R = RAM-heavy workloads.
Q10. What are Graviton instances, and how do they differ from Intel-based instances?
1. Simple Concept
AWS Graviton processors are AWS-designed Arm-based processors. Intel-based EC2 instances use the x86-64 architecture.
2. Why We Need It
Graviton can offer attractive price-performance for supported workloads, but migration requires compatibility testing.
3. How It Works
The CPU architecture determines which operating systems, binaries, libraries, and container images can run natively.
4. Production Example
An application currently runs on an Intel-based instance. Before moving it to Graviton, you verify its dependencies, build an Arm64 container image, and benchmark performance.
5. Command / Configuration
uname -m
docker image inspect <image-name>Linux commonly reports x86_64 for x86-64 and aarch64 for 64-bit Arm.
6. Common Interview Trap
Assuming every application or Docker image will run unchanged on Arm. Native binaries and third-party dependencies may need compatible builds.
7. Candidate-Style Answer
“Graviton uses AWS-designed Arm-based processors, whereas Intel instances use x86-64 processors. Graviton can provide strong price-performance, but I would validate operating system support, application dependencies, container architecture, and performance before migrating.”
8. Memory Trick
Graviton = Arm. Intel = x86-64. Compatibility comes first.
Section 3: AWS Networking
Q11. What is AWS Direct Connect?
1. Simple Concept
AWS Direct Connect provides dedicated network connectivity between an organization’s network and AWS.
2. Why We Need It
Organizations may require private connectivity, predictable network performance, or high-bandwidth access between on-premises systems and AWS.
3. How It Works
A connection is provisioned through an AWS Direct Connect location. Virtual interfaces and routing configurations provide access to supported AWS network services.
4. Production Example
An enterprise connects its on-premises data center to AWS to access private application infrastructure.
5. Command / Configuration
Review connections and their states:
aws directconnect describe-connections
aws directconnect describe-virtual-interfaces6. Common Interview Trap
Assuming Direct Connect automatically encrypts traffic. Direct Connect is not inherently encrypted. Use appropriate encryption when required.
7. Candidate-Style Answer
“AWS Direct Connect provides dedicated connectivity between an organization’s network and AWS. It can offer more consistent performance and private network connectivity than internet-based connections. I would also verify routing, redundancy, and encryption requirements.”
8. Memory Trick
Direct Connect = dedicated network path to AWS.
Q12. What is a Direct Connect Gateway?
1. Simple Concept
A Direct Connect Gateway helps connect a Direct Connect connection to supported AWS network environments across multiple Regions.
2. Why We Need It
Organizations often need connectivity between on-premises networks and VPCs in multiple AWS Regions.
3. How It Works
A Direct Connect Gateway can associate with supported virtual private gateways or Transit Gateways, subject to AWS configuration and routing requirements.
4. Production Example
A company needs to connect its data center to private workloads in multiple AWS Regions through a centrally managed network design.
5. Command / Configuration
aws directconnect describe-direct-connect-gateways6. Common Interview Trap
Assuming the gateway automatically creates routes or provides unrestricted connectivity to every VPC. Associations and routing must be configured correctly.
7. Candidate-Style Answer
“A Direct Connect Gateway allows a Direct Connect connection to reach supported AWS network environments across multiple Regions. It simplifies connectivity architecture, but I would still validate associations, route advertisements, and network reachability.”
8. Memory Trick
Connection provides the path; gateway connects it to supported AWS network environments.
Q13. What is the difference between Dedicated and Hosted Direct Connect?
1. Simple Concept
A Dedicated connection is a physical connection provisioned for one customer. A Hosted connection is provided through an AWS Direct Connect Partner.
2. Why We Need It
The two options serve different bandwidth, provisioning, and connectivity requirements.
3. How It Works
With a Dedicated connection, the customer requests a dedicated port. With a Hosted connection, a partner provisions connectivity using its Direct Connect infrastructure.
4. Production Example
A large enterprise may require a dedicated connection, while a smaller organization may obtain connectivity through a partner.
5. Command / Configuration
aws directconnect describe-connections
aws directconnect describe-virtual-interfacesUse these commands to inspect connection and virtual-interface information.
6. Common Interview Trap
Assuming Hosted and Dedicated connections have identical capacity options. Available speeds and capabilities depend on the offering and provider.
7. Candidate-Style Answer
“A Dedicated connection provides a dedicated physical port for the customer. A Hosted connection is delivered through a Direct Connect Partner. I would compare bandwidth, cost, provisioning, availability, and the customer’s connectivity requirements before choosing.”
8. Memory Trick
Dedicated = dedicated physical port. Hosted = partner-provisioned connectivity.
Q14. Explain AWS Regions, Availability Zones, and IAM.
1. Simple Concept
A Region is a geographic AWS area, an Availability Zone is an isolated location within a Region, and IAM manages identities and permissions.
2. Why We Need It
Regions support geographic deployment choices, Availability Zones improve resilience, and IAM controls access to AWS resources.
3. How It Works
Applications can be deployed across multiple AZs for resilience. IAM policies define what identities can do, while roles provide temporary credentials to authorized workloads and users.
4. Production Example
An application runs across two AZs behind a load balancer. EC2 workloads use an IAM role to access an S3 bucket without storing long-lived access keys.
5. Command / Configuration
aws ec2 describe-availability-zones
aws sts get-caller-identity
aws iam list-roles6. Common Interview Trap
Assuming IAM is tied to one Availability Zone. IAM is a global service, whereas many infrastructure resources are Region-specific.
7. Candidate-Style Answer
“A Region is a geographic AWS area, while an Availability Zone is an isolated location within that Region. IAM manages access through identities, roles, and policies. I would deploy critical workloads across AZs and apply least-privilege IAM permissions.”
8. Memory Trick
Region = geography. AZ = isolation. IAM = access control.
Q15. What are the default ports for MySQL, MongoDB, HTTP, HTTPS, SSH, and SFTP?
1. Simple Concept
A port identifies a network service endpoint on a host.
2. Why We Need It
Knowing default ports helps configure firewalls, Security Groups, connectivity tests, and service monitoring.
3. How It Works
Clients connect to a server IP address and port using the relevant protocol.
4. Production Example
An application cannot connect to MySQL because TCP port 3306 is blocked between the application and database subnets.
5. Command / Configuration
nc -vz <host> 3306
nc -vz <host> 27017
nc -vz <host> 443Default ports to remember:
HTTP: 80
HTTPS: 443
SSH: 22
SFTP: 22 by default
MySQL: 3306
MongoDB: 27017
6. Common Interview Trap
Confusing SFTP with FTP. SFTP normally runs over SSH on port 22, while FTP commonly uses port 21 and separate data-channel arrangements.
7. Candidate-Style Answer
“HTTP uses port 80, HTTPS uses 443, SSH and SFTP normally use 22, MySQL uses 3306, and MongoDB commonly uses 27017. I would verify the actual service configuration because ports can be customized.”
8. Memory Trick
Web: 80/443. SSH/SFTP: 22. MySQL: 3306. MongoDB: 27017.
Q16. Explain Security Group inbound and outbound rules.
1. Simple Concept
An AWS Security Group is a stateful virtual firewall associated with supported network interfaces and resources.
2. Why We Need It
Security Groups control which network connections are permitted to reach a resource and which outbound connections it can initiate.
3. How It Works
Inbound rules allow specified incoming traffic. Outbound rules allow specified outgoing traffic. Security Groups are stateful, so return traffic for an allowed connection is automatically permitted.
4. Production Example
A web server accepts HTTPS from clients, while SSH is restricted to an administrative IP range. A database Security Group permits MySQL traffic only from the application Security Group.
5. Command / Configuration
aws ec2 describe-security-groups \
--group-ids sg-xxxxxxxxxxxxxxxxx6. Common Interview Trap
Opening all ports to 0.0.0.0/0 to solve a connectivity problem. That exposes the resource unnecessarily.
7. Candidate-Style Answer
“Inbound rules control incoming connections and outbound rules control outgoing connections. Security Groups are stateful. I would allow only the required protocols, ports, and sources, preferably using Security Group references for communication between application tiers.”
8. Memory Trick
Inbound = entering. Outbound = leaving. Stateful = return traffic is tracked.
Q17. A Security Group port is open, but the application is unreachable. How do you troubleshoot?
1. Simple Concept
Connectivity depends on the entire network path and the application, not just the Security Group.
2. Why We Need It
A port can be allowed at the Security Group level while another component prevents communication.
3. How It Works
Check the application listener, host firewall, network routing, Network ACLs, IP addressing, DNS, and any load balancer in the path.
4. Production Example
Port 443 is allowed, but the application listens only on 127.0.0.1:443. Remote clients cannot reach the listener through the instance’s network interface.
5. Command / Configuration
sudo ss -lntp
sudo systemctl status nginx
curl -v http://localhost:8080
ip route
nc -vz <server-ip> 443Also check:
Security Group rules.
Network ACL inbound and outbound rules.
Route tables and Internet Gateway or NAT requirements.
Public/private IP and DNS configuration.
Host firewall configuration.
Load balancer listener and target health.
Application logs and listening interface.
6. Common Interview Trap
Immediately opening additional ports without identifying the failing layer.
7. Candidate-Style Answer
“I would first confirm that the application is running and listening on the expected port. Then I would test local and remote connectivity, verify Security Groups and Network ACLs, inspect route tables and IP configuration, and check the host firewall and load balancer. I would isolate the failing component before changing configuration.”
8. Memory Trick
Application → Listener → Host Firewall → Security Group → NACL → Route → Destination.
Q18. How do you check network connectivity using Linux commands and package managers?
1. Simple Concept
Linux networking tools help diagnose DNS, routing, listening ports, and remote connectivity.
2. Why We Need It
They help distinguish application failures from DNS, routing, firewall, and transport-level problems.
3. How It Works
Inspect interfaces and routes, resolve hostnames, check listeners, test TCP connections, and review the output of network tools.
4. Production Example
A service cannot connect to an external HTTPS endpoint. You verify DNS resolution, route configuration, and TCP connectivity to port 443 before investigating TLS or application-level failures.
5. Command / Configuration
ip addr
ip route
ss -lntp
getent hosts example.com
curl -Iv https://example.com
nc -vz example.com 443Package installation examples:
# Ubuntu / Debian
sudo apt update
sudo apt install curl netcat-openbsd traceroute
# Amazon Linux 2023 / RHEL-family systems
sudo dnf install curl nmap-ncat traceroute6. Common Interview Trap
Assuming that a failed ping proves a server is unreachable. ICMP may be blocked while TCP connectivity still works.
7. Candidate-Style Answer
“I use ip and ip route to check interfaces and routing, getent to test DNS resolution, ss to inspect listeners, and curl or nc to test connectivity. I install the required tools using the package manager supported by the Linux distribution.”
8. Memory Trick
IP → Route → DNS → Port → Application.
Section 4: Amazon S3
Q19. Explain S3 Lifecycle, expiration rules, S3 vs. EBS, and S3 Files.
1. Simple Concept
Amazon S3 is object storage. EBS is block storage. S3 Lifecycle rules automate object transitions and expiration.
2. Why We Need It
S3 supports scalable object storage, while Lifecycle rules can reduce storage costs and enforce retention policies.
3. How It Works
Lifecycle configurations define rules for eligible objects. Objects can transition between supported storage classes or expire according to configured policies.
S3 File Gateway, part of AWS Storage Gateway, provides file-based access to S3 through a file interface. The phrase “S3 Files” should be clarified because it is not the formal name of a single S3 storage class or service.
4. Production Example
An organization keeps recent application logs in S3 Standard, transitions older logs to an archival storage class, and expires eligible objects after its retention period.
5. Command / Configuration
Inspect an S3 Lifecycle configuration:
aws s3api get-bucket-lifecycle-configuration \
--bucket <bucket-name>6. Common Interview Trap
Assuming that S3 and EBS are interchangeable. S3 stores objects through APIs; EBS provides block devices that can host filesystems.
7. Candidate-Style Answer
“S3 is object storage for backups, logs, media, and other objects. EBS is block storage commonly used by EC2 operating systems and applications. S3 Lifecycle rules automate transitions and expiration. If the requirement is file-based access to S3, I would clarify whether the interviewer means S3 File Gateway.”
8. Memory Trick
S3 = objects. EBS = blocks. Lifecycle = automated storage management.
Q20. Explain S3 storage classes and moving objects between them.
1. Simple Concept
S3 storage classes provide different cost, access, and availability characteristics for stored objects.
2. Why We Need It
Not all data is accessed equally. Choosing appropriate storage classes can reduce costs while meeting access and retention requirements.
3. How It Works
Lifecycle rules or explicit object operations can move eligible objects between supported storage classes.
Common classes include:
S3 Standard for frequently accessed data.
S3 Intelligent-Tiering for changing or unpredictable access patterns.
S3 Standard-IA for infrequently accessed data requiring rapid access.
S3 One Zone-IA for infrequently accessed data stored in one AZ.
S3 Glacier Instant Retrieval for archival data requiring millisecond access.
S3 Glacier Flexible Retrieval for archival data where longer retrieval times are acceptable.
S3 Glacier Deep Archive for long-term archival with slower retrieval.
4. Production Example
Older compliance records are transitioned to an archival class based on retention requirements, while frequently accessed application assets remain in S3 Standard.
5. Command / Configuration
Copy an object while changing its storage class:
aws s3 cp \
s3://source-bucket/example.log \
s3://destination-bucket/example.log \
--storage-class STANDARD_IAThis example creates a copy in the destination bucket. For a same-bucket transition, configure the appropriate destination and copy options or use Lifecycle rules. Check object metadata, encryption, permissions, and versioning requirements.
6. Common Interview Trap
Choosing the lowest storage price without considering retrieval charges, minimum storage duration, availability, and access latency.
7. Candidate-Style Answer
“S3 offers storage classes for different access patterns. I would choose a class based on how frequently data is accessed, how quickly it must be retrieved, durability and availability requirements, and total cost. I would use Lifecycle rules to automate transitions where appropriate.”
8. Memory Trick
Frequent access → Standard. Variable access → Intelligent-Tiering. Rare access → IA or Glacier, depending on retrieval needs.
Section 5: MySQL and MongoDB
Q21. Explain your MySQL and MongoDB experience.
1. Simple Concept
MySQL is a relational database that organizes data in tables. MongoDB is a document-oriented database that stores BSON documents in collections.
2. Why We Need It
Applications use databases to store, retrieve, and manage persistent data.
3. How It Works
MySQL uses SQL, schemas, and relational operations. MongoDB supports document queries and indexes, with data organized into collections.
4. Production Example
An application uses MySQL for transactional records and MongoDB for document-oriented data. Both databases require appropriate indexes, backups, access controls, and monitoring.
5. Command / Configuration
MySQL:
SELECT VERSION();
SHOW DATABASES;
SHOW FULL PROCESSLIST;MongoDB:
db.version()
show dbs
db.serverStatus()6. Common Interview Trap
Claiming advanced production database administration experience when your experience is limited to basic queries or a local lab.
7. Candidate-Style Answer
“MySQL is a relational database that uses tables and SQL, while MongoDB is a document-oriented database that stores BSON documents. My troubleshooting approach includes checking connectivity, authentication, resource usage, query performance, indexes, logs, and replication health.”
8. Memory Trick
MySQL = relational tables. MongoDB = document-oriented collections.
Q22. How do you troubleshoot production MySQL or MongoDB servers?
1. Simple Concept
Database troubleshooting identifies the cause of slow queries, connection failures, replication issues, or database unavailability.
2. Why We Need It
Database problems can affect application performance, data availability, and business operations.
3. How It Works
Start with the symptoms, then inspect host resources, database connections, query performance, logs, network connectivity, and replication state.
4. Production Example
An application reports database timeouts. You discover that the connection pool is exhausted and several queries are taking much longer than usual.
5. Command / Configuration
Linux:
uptime
free -h
df -h
iostat -xz 1MySQL:
SHOW FULL PROCESSLIST;
SHOW GLOBAL STATUS;
SHOW VARIABLES LIKE 'max_connections';MongoDB:
db.serverStatus()
db.currentOp()
db.stats()Use the relevant commands and permissions for your installed database version.
6. Common Interview Trap
Restarting the database immediately without gathering evidence. A restart can interrupt service and erase useful diagnostic context.
7. Candidate-Style Answer
“I would assess the impact, check CPU, memory, disk space, and I/O, then inspect database connections, slow queries, locks, logs, and replication health. I would identify the root cause, apply a controlled fix, and verify that application performance and database health recover.”
8. Memory Trick
Host → Connections → Queries → Logs → Replication → Recovery.
Q23. How do you configure MySQL source-replica replication on two EC2 instances?
1. Simple Concept
MySQL replication copies changes from a source database to one or more replicas.
2. Why We Need It
Replication can support read scaling, reporting workloads, and certain availability or recovery architectures.
3. How It Works
Configure unique server IDs, enable binary logging on the source, create a replication account, establish a consistent initial data copy, configure the replica’s source connection, and start replication.
Exact syntax depends on the MySQL version and whether file-position-based replication or GTID-based replication is used.
4. Production Example
An application sends writes to the source database while read-only reporting queries run against a replica. Monitoring detects replication lag before the reporting data becomes too stale.
5. Command / Configuration
Check MySQL replication status using commands appropriate to the version:
SHOW REPLICA STATUS\GOn older MySQL versions, SHOW SLAVE STATUS may be used.
Inspect replication-related configuration:
SHOW VARIABLES LIKE 'server_id';
SHOW VARIABLES LIKE 'log_bin';6. Common Interview Trap
Assuming replication is a backup. Replication can copy accidental deletions or corrupted changes. Maintain independent backups and test restoration.
7. Candidate-Style Answer
“I would configure two compatible MySQL instances, assign unique server IDs, enable binary logging on the source, and create a dedicated replication user. I would establish a consistent initial data copy, configure replication using the correct log coordinates or GTID state, start the replica, and verify replication status and lag.”
8. Memory Trick
Configure → Seed → Connect → Replicate → Verify → Monitor.
Section 6: Linux Administration
Q24. What is /proc in Linux?
1. Simple Concept
/proc is a virtual filesystem that exposes information about running processes and kernel state.
2. Why We Need It
It provides useful diagnostic information about processes, CPU, memory, and system operation.
3. How It Works
The kernel exposes structured information through files and directories under /proc. Many entries represent live system state rather than ordinary files stored on disk.
4. Production Example
A server experiences memory pressure. You inspect /proc/meminfo and process-specific entries to investigate memory consumption.
5. Command / Configuration
cat /proc/cpuinfo
cat /proc/meminfo
cat /proc/uptime
ls /proc6. Common Interview Trap
Assuming /proc is an ordinary directory containing permanent application files.
7. Candidate-Style Answer
“/proc is a virtual filesystem provided by the Linux kernel. It exposes information about processes and system state. I use it to inspect CPU, memory, uptime, and process-specific information during troubleshooting.”
8. Memory Trick
/proc = a window into processes and kernel state.
Q25. Which Linux commands do you use every day?
1. Simple Concept
Linux commands help inspect system health, manage files, control services, and troubleshoot applications.
2. Why We Need It
Cloud support engineers must investigate problems quickly, often through a terminal without a graphical interface.
3. How It Works
Different commands reveal different layers of system behaviour, including resource usage, filesystems, processes, services, logs, and networking.
4. Production Example
A disk alert fires. You use df to identify the affected filesystem and du to find which directory is consuming space.
5. Command / Configuration
# System health
uptime
top
free -h
# Disk
df -h
du -sh /var/log/*
# Processes and services
ps aux
systemctl --failed
journalctl -p err -b
# Files and permissions
find /var/log -type f
stat application.log6. Common Interview Trap
Running commands without understanding their output or the risks of modifying production files.
7. Candidate-Style Answer
“I use commands such as top, free, df, du, ps, systemctl, journalctl, ss, and find to investigate system health, storage, services, logs, and connectivity. I choose commands based on the symptom and avoid making changes before understanding the issue.”
8. Memory Trick
Resources → Processes → Storage → Services → Logs → Network.
Q26. What is the difference between chown and chmod?
1. Simple Concept
chown changes ownership. chmod changes permissions.
2. Why We Need It
Applications require correct file ownership and permissions to read configuration files, write logs, and access required directories.
3. How It Works
Ownership determines the user and group associated with a file. Permissions determine what the owner, group, and other users can do.
4. Production Example
An application cannot write to its log directory because the directory is owned by the wrong user or lacks the necessary write permission.
5. Command / Configuration
sudo chown appuser:appgroup application.log
sudo chmod 640 application.log
stat application.log6. Common Interview Trap
Using chmod 777 as a universal fix. This grants excessive access and can introduce security risks.
7. Candidate-Style Answer
“chown changes the owner or group of a file, while chmod changes its permissions. I would inspect the current ownership and permission bits, identify the application user, and apply the minimum permissions required.”
8. Memory Trick
CHOWN = ownership. CHMOD = mode or permissions.
Section 7: Containers and Infrastructure as Code
Q27. Explain Kubernetes architecture and Docker images.
1. Simple Concept
Kubernetes orchestrates containerized applications across a cluster. A Docker image packages application files, dependencies, and metadata into a reusable template.
2. Why We Need It
Containers help package applications consistently, while Kubernetes manages scheduling, scaling, service discovery, and workload recovery.
3. How It Works
The Kubernetes control plane manages desired cluster state. Worker nodes run Pods using a container runtime. Images are pulled from registries when workloads require them.
4. Production Example
A deployment creates several application Pods. If a Pod fails, Kubernetes can replace it to maintain the desired replica count, provided the cluster has sufficient capacity and the workload is configured correctly.
5. Command / Configuration
kubectl get nodes
kubectl get pods -A
kubectl describe pod <pod-name>
kubectl logs <pod-name>
docker images
docker ps6. Common Interview Trap
Confusing an image with a container. An image is the template; a container is an instance created from that image.
7. Candidate-Style Answer
“Kubernetes manages containerized workloads across a cluster. The control plane maintains desired state and schedules workloads, while worker nodes run Pods. Docker images package application dependencies and provide the template used to start containers.”
8. Memory Trick
Image = package. Container = running instance. Kubernetes = orchestrator.
Q28. What is the difference between master and worker nodes?
1. Simple Concept
The control plane manages Kubernetes cluster state, while worker nodes run application workloads.
2. Why We Need It
Separating orchestration from workload execution helps organize cluster management and application operations.
3. How It Works
Control-plane components include the API server, scheduler, controller manager, and etcd. Worker nodes run components such as kubelet and a container runtime.
4. Production Example
In Amazon EKS, AWS manages the Kubernetes control plane, while the customer remains responsible for workload configuration and the worker capacity model they choose.
5. Command / Configuration
kubectl get nodes -o wide
kubectl describe node <node-name>6. Common Interview Trap
Assuming the customer manages every control-plane component in EKS. EKS is a managed Kubernetes service.
7. Candidate-Style Answer
“The control plane manages scheduling, cluster state, and orchestration. Worker nodes run application Pods. In EKS, AWS manages the control plane, while customers manage their workloads and worker capacity according to their architecture.”
8. Memory Trick
Control plane coordinates; worker nodes execute workloads.
Q29. What is the difference between CloudFormation and Terraform?
1. Simple Concept
Both are Infrastructure as Code tools used to define and manage infrastructure through configuration files.
2. Why We Need It
Infrastructure as Code makes infrastructure changes repeatable, reviewable, and easier to automate.
3. How It Works
CloudFormation uses AWS-managed stacks and templates. Terraform uses configuration files, providers, plans, and state to manage resources across supported platforms.
4. Production Example
A team uses Terraform modules to create VPCs, EKS clusters, and IAM roles across environments. Another team uses CloudFormation stacks to manage AWS-native infrastructure.
5. Command / Configuration
Terraform:
terraform init
terraform validate
terraform plan
terraform applyCloudFormation:
aws cloudformation describe-stacks
aws cloudformation describe-stack-events \
--stack-name <stack-name>6. Common Interview Trap
Treating Terraform state as an ordinary backup file. State maps managed resources to configuration and must be secured and managed carefully.
7. Candidate-Style Answer
“CloudFormation is AWS-native Infrastructure as Code, while Terraform supports multiple cloud providers through its provider model. CloudFormation manages stacks, and Terraform uses configuration, plans, and state. I would choose based on platform requirements, team expertise, ecosystem, and operational needs.”
8. Memory Trick
CloudFormation = AWS-native stacks. Terraform = provider-based IaC with state.
Section 8: Monitoring and Web Servers
Q30. Which monitoring tools have you used?
1. Simple Concept
Monitoring tools collect and present information about infrastructure and application health.
2. Why We Need It
Monitoring helps detect failures, identify performance bottlenecks, and investigate incidents before they cause larger outages.
3. How It Works
Metrics show measurable behaviour, logs record events, and dashboards or alerts help engineers recognize abnormal conditions.
4. Production Example
A service becomes slow. CloudWatch or Prometheus reveals increased latency and CPU usage, while application logs identify repeated timeout errors.
5. Command / Configuration
aws cloudwatch list-metrics
kubectl top nodes
kubectl top podskubectl top requires a functioning metrics pipeline, commonly Metrics Server.
Tools worth understanding include:
Amazon CloudWatch for AWS metrics, logs, alarms, and dashboards.
Prometheus for metrics collection and querying.
Grafana for dashboards and visualization.
ELK Stack for log ingestion, search, and analysis.
6. Common Interview Trap
Listing monitoring tools without explaining which metrics, logs, alerts, or incidents you investigated.
7. Candidate-Style Answer
“I use monitoring to understand system health, detect abnormal behaviour, and investigate incidents. I correlate metrics, logs, and recent changes to identify potential root causes, then validate the recovery after applying a fix.”
8. Memory Trick
Metrics show trends. Logs explain events. Alerts highlight conditions requiring attention.
Q31. What is a web server? Explain Apache HTTPD.
1. Simple Concept
A web server accepts HTTP or HTTPS requests and serves content or forwards requests to application components. Apache HTTP Server is a widely used web server.
2. Why We Need It
Web servers handle incoming requests, serve static content, and can integrate with application backends.
3. How It Works
A client sends an HTTP request. Apache processes the request according to its configuration and serves content or forwards it through the configured application integration.
4. Production Example
A website starts returning HTTP 500 errors. You inspect Apache logs, configuration, permissions, and the health of upstream application services.
5. Command / Configuration
Amazon Linux and many RHEL-based systems:
sudo systemctl status httpd
sudo httpd -t
sudo journalctl -u httpd --since "30 minutes ago"Ubuntu commonly uses the apache2 service name:
sudo systemctl status apache2
sudo apache2ctl configtest6. Common Interview Trap
Assuming every HTTP 500 error originates in Apache. The application backend or another dependency may be responsible.
7. Candidate-Style Answer
“Apache HTTP Server handles HTTP requests and can serve static content or integrate with application backends. When troubleshooting, I check service status, configuration syntax, logs, permissions, listening ports, and upstream application health.”
8. Memory Trick
Request → Web server → Application or content → Response.
Q32. Explain load balancers, ALB vs. NLB, reverse proxy vs. forward proxy.
1. Simple Concept
A load balancer distributes traffic across targets. A proxy forwards requests between clients and other systems.
2. Why We Need It
Load balancing improves traffic distribution and availability. Proxies provide routing, access control, and other network functions.
3. How It Works
An Application Load Balancer operates at Layer 7 and supports HTTP/HTTPS-aware routing. A Network Load Balancer operates primarily at Layer 4 and supports TCP, UDP, and TLS listener use cases, depending on configuration.
A reverse proxy represents backend servers to clients. A forward proxy represents clients when accessing external destinations.
4. Production Example
An ALB routes /api requests to one target group and /web requests to another. A forward proxy, by contrast, may control employees’ outbound web access.
5. Command / Configuration
Inspect load balancers:
aws elbv2 describe-load-balancers
aws elbv2 describe-target-health \
--target-group-arn <target-group-arn>6. Common Interview Trap
Choosing ALB or NLB based only on popularity. Consider protocol, routing requirements, TLS handling, performance, and application architecture.
7. Candidate-Style Answer
“An ALB provides Layer 7 routing for HTTP and HTTPS applications, while an NLB supports Layer 4 traffic patterns such as TCP and UDP, subject to listener configuration. A reverse proxy forwards incoming client requests to backend servers, while a forward proxy mediates clients’ outbound requests.”
8. Memory Trick
ALB = application-aware routing. NLB = network-level traffic. Reverse proxy = backend-facing. Forward proxy = client-facing.
Final Interview Preparation Strategy
For every AWS Cloud Support L2 question, prepare all eight attributes:
Simple Concept: Explain the technology in plain language.
Why We Need It: Describe the problem it solves.
How It Works: Explain the underlying mechanism.
Production Example: Connect it to a realistic situation.
Command / Configuration: Demonstrate how you would inspect or configure it.
Common Interview Trap: Explain a frequent misconception or risky approach.
Candidate-Style Answer: Deliver a concise response as you would in an interview.
Memory Trick: Create a simple way to recall the key distinction.
You do not need to recite all eight headings during the interview. Use them to prepare a complete answer, then explain it naturally.
Final Takeaway
This interview experience highlights an important lesson for AWS Cloud Support L2 candidates: knowing the definition is the starting point, not the finish line.
Practise troubleshooting EC2 and EBS issues. Understand network routing beyond Security Groups. Learn Linux commands well enough to investigate production symptoms. Understand database replication, container architecture, and Infrastructure as Code.
Most importantly, explain your reasoning clearly.
When an interviewer presents an unfamiliar problem, demonstrate how you gather evidence, isolate the fault, validate a solution, and reduce the risk of recurrence.
That is how you move from memorizing AWS interview questions to thinking like a cloud support engineer.
Explore More DevOps Learning Resources
Explore practical DevOps courses, interview guides, enterprise projects, and troubleshooting resources.
Topmate: https://topmate.io/arvindverma021/
LinkedIn: https://www.linkedin.com/in/arvindverma021/
Medium: https://medium.com/@arvindverma021
Substack:
#AWS #AWSCloudSupport #WiproInterview #CloudSupport #AWSInterview #Linux #Networking #EC2 #Kubernetes #Terraform #DevOps #CloudComputing #InterviewPreparation #TechCareers
Arvind Verma is free today. But if you enjoyed this post, you can tell Arvind Verma that their writing is valuable by pledging a future subscription. You won't be charged unless they enable payments.
© 2026 Arvind Verma
548 Market Street PMB 72296, San Francisco, CA 94104