LFCA Practice Questions

Recovery Point Objective (RPO) refers to the maximum acceptable amount of data loss, measured in time. In this case, it's 4 hours. Recovery Time Objective (RTO) is the target time within which a business process must be restored after a disaster to avoid unacceptable consequences. Here, it's 2 hours. Therefore, the RPO is 4 hours and the RTO is 2 hours.

This describes a specific action the system must be able to perform, which is the definition of a functional requirement.

This describes a core feature or function of the banking portal, defining 'what' the system does.

Spot Instances allow cloud users to bid on spare computing capacity, offering the largest discounts but with the caveat that the instance can be terminated by the provider with short notice. This model is perfect for fault-tolerant, flexible workloads like batch processing, where interruptions can be handled and the job can be restarted.

The CIA Triad is a foundational model in information security. It consists of three core principles: Confidentiality (preventing unauthorized disclosure), Integrity (ensuring data is accurate and trustworthy), and Availability (ensuring data and services are accessible to authorized users when needed).

A Pod is the fundamental building block in Kubernetes. It represents a single instance of a running process in a cluster and can contain one or more tightly coupled containers that share storage and network resources. While containers run inside Pods, the Pod itself is the atomic unit of deployment and scheduling.

The Waterfall methodology is the most appropriate choice. This model is sequential and requires that each phase (requirements, design, implementation, testing) be fully completed before the next begins. It is ideal for projects where requirements are well-understood, fixed, and unlikely to change, which is the case here due to regulatory pre-approval. Scrum and Kanban are Agile methodologies that are better suited for projects with evolving requirements.

Function as a Service (FaaS), also known as Serverless computing, is the ideal model. It allows developers to upload and execute code (functions) without managing any underlying infrastructure. The platform handles scaling, patching, and server management automatically. PaaS is a close second, but FaaS better represents the concept of focusing purely on application logic and automatic scaling from zero.

fail2ban is an intrusion prevention software framework that protects computer servers from brute-force attacks. It works by monitoring log files (e.g., /var/log/auth.log) for patterns of failed login attempts and uses the system firewall to block the offending IP addresses. While ufw and iptables are firewalls that fail2ban can use to block IPs, they do not perform the log scanning and automated blocking themselves.

The git rebase command is used to re-apply commits from one branch on top of another. By checking out the feature branch and running git rebase main, the developer effectively moves the entire feature branch to begin on the tip of the main branch, incorporating its updates and maintaining a linear history. git merge main would create a merge commit, which violates the stated requirement.

This is a non-functional requirement. Functional requirements define what a system should do (e.g., 'a user must be able to add items to a cart'). Non-functional requirements define how a system should perform a function, specifying criteria like performance, security, and reliability. The ability to handle 1,000 transactions per second is a performance criterion.