Відео

This is networking related questions. May I know how is this related to Cloud ?

Ha said in the video that he havent got 60% in enginerring But in the resume its 8.02 😂

Speaks confidently and has sound knowledge too. RDS is a SQL DB which has a schema while DynamoDb is a NoSql DB which uses key value pair and it does not have a schema. RDS can be created in VPC while DynamoDb cannot be created. If an application has to access an the DynamoDb it will be accessed thru an VPC Endpoint in the most secure way. There are 2 types of Endpoints Gateway and Interface . For DynamoDb a Gateway Endpoint has to be created

Sir perform some linux and bash interview

Awesome 🎉

Link not working

What will be package for this knowledge

Thanks for your valuable information...

Very insightful and concise sharing of topics. The added perks of Git repo, UA-cam channel, and certification ideas are particularly valuable. They've given me a clear roadmap for further exploration. Thank you for your valuable guidance.🙏🙏

Very helpful video

Im from non cloud domain, I can answer better than him. Hard to believe he is an AWS engineer

Default port of http is 80 and for https it is 443 One of the major difference between.

I have 2 years of experience in other domain and want to switch devops now. How can i portray this?

Sir already have 5years of experience in security as incident response. Now not interested to move into the same. So trying to move into cloud engineer role. How cloud engineer is different from devops right now in industry. Suggest me the right path and skills and tools to be leaent for cloud engineering role.

true advice

18:36 You Are From 😂😂

Such a genuine and to the point advice 👏🙌

very well said.....

True❤❤❤

I've been working in IT industry for more than 8+ years and there's absolutely no way this guy is fresher. No university teaches you all these concepts + surfing youtube alone or completing courses on udemy or udacity, won't give you that much information on each and every tool until and unless you have hands-on experience of at least 5+ years in DevOps. Looking at his age, he looks like a fresher but this interview is most likely a setup, those who are professionally working in the market can understand what I meant.

Redshift data warehousing

A fresher goes to deveops field??

Nah he definitely a junior at least

Do we need to mention experience of Devops engineer or as a fresher on resume. I have 10 Year experience into IT Support Engineer, I did devops. Kindly guide me. Because i get senior level or Lead level interviews.

Once we done a devops course, Should we mentioned experience(3yrs) devops engineer or fresher. I am little confuse. Earlier I worked as a IT Support Engineer.

how to connect you ?

How should we contact you guys

Really nice suggestion sir.

The boundary will be our loadbalancer

❤

Switching to business license is not a bad step , many enterprise organizations prefer business licenses than Open source licensed products , especially the enterprise support that comes with the business licenses , think about it , would you run production grade systems on Open source products relying the source code that is open to the world with limited developer support or using business licensed products. Example Production grade systems run on Red Hat Enterprise servers and not on boot leg Rocky Linux.

Only left side audio

Sanjeev never makes us unsatisfied in regard to providing content.

Dude needs to practice more

Good videos pls upload more.

1. What is Kubernetes? Kubernetes is an orchestration tool that is used to manage containerization applications and it can also interact with VMs to some extent. Kubernetes is specifically designed to automate the deployments, scaling, and management of containerized applications. 2. What are the key components of a Kubernetes cluster? In master node/control plane:- API server, Clusture store/etcd database, Scheduler, Controller. In worker node:- Kubelet, Docker, Kubeproxy, pods, and containers inside pods. 3. What is the purpose of Kubernetes pods? *The purpose of Kubernetes pods is to create container inside it. It can be single-container or multi-container pods. *We use pods to deploy the applications inside it which are isolated from each other, and easy to function independently. *We can scale up and scale down the pods based on traffic and it can be managed by load balancer. * Pods share the same network namespaces so they can communicate with each other over localhost. * Pods share storage resources through volume. Overall, Kubernetes pods provide a convenient abstraction that manages groups of containers and its work together so application can run fine. 4. In Kubernetes, the application runs inside pods. Think of the application as the big picture-it's what you want to achieve, like running a website or a database service. Then, the pods are like the containers that hold all the pieces needed to make that application work. These pieces could be the main program, databases, cache servers, or anything else your application needs. The pods share everything they have with each other, like internet access, storage, and settings, because they're all part of the same application. So, when you create and run an application in Kubernetes, you're actually running it inside pods, which handle all the nitty-gritty details of making your application work smoothly. 5. Horizontal Scaling: Monitoring: As a DevOps engineer, you'd keep an eye on your application's performance indicators, like CPU and memory usage, using monitoring tools. Adding More Pods: When demand increases, you'd spin up additional pod replicas to handle the extra load. This can be done manually or automatically with tools like Horizontal Pod Autoscaler. Balancing the Load: To ensure all pods share the load evenly, you'd configure a load balancer to distribute incoming traffic across the newly added replicas. Testing and Tweaking: Before letting the new replicas handle production traffic, you'd run tests to make sure they're functioning properly and can handle the increased load. Ongoing Monitoring: Even after scaling, you'd keep a close watch on your application's performance, adjusting pod counts as needed to meet changing demand. Vertical Scaling: Monitoring Resource Usage: You'd monitor resource consumption within your pods to identify any bottlenecks, such as CPU or memory constraints. Adjusting Resources: To alleviate resource constraints, you'd tweak the allocated CPU and memory for individual pods, usually by updating your Kubernetes configuration files. Restarting Pods: Sometimes, adjusting resources requires restarting pods to apply changes. Kubernetes handles this for you automatically. Validation and Optimization: After resource adjustments, you'd validate the impact on your application's performance through testing and monitoring, making further adjustments as needed. Fine-Tuning Over Time: Continuous monitoring and feedback loops would guide you in fine-tuning your resource allocations to maintain optimal performance and resource utilization over time.

Great interview. Thanks guys

Thank you for your effort & time. These mockup interview videos help us a lot.

All Major companis are moving back to on premises from cloud. What will the job role for devops or cloud enginer ? Pease support on this .

done

audio issue

Please share with me Sir above is my mail id

1. Ansible playbook is yaml file that contains sets of instruction to automation task. 2. Ansible is simple then other tools as written in yaml. Also it doesn't require any agent to be installed on nodes it works with ssh 3. Ad-hoc commands are simple and are for one time use only. Whereas playbook has more complex command or series of commands.

😂😂😂why that fake accent, he is not coming to point directly

Appreciate the patience of interviewer😊

Wow... Impressive... The way he explains, his confidence my god... He doesn't feel like fresher!

Some wrong answer be told i think

He is cheating ?

Please attach this candidate cv