Free LFCA sample questions

Correct answer: Waterfall

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.

Correct answer: Function as a Service (FaaS) / Serverless

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.

Correct answer: fail2ban

`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.

Correct answer: git rebase main

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.

Correct answer: Non-Functional 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.

Correct answer: It is the default behavior of rsync

The core functionality of `rsync` is its delta-transfer algorithm, which is enabled by default. This algorithm intelligently calculates the differences between the source and destination files and only transfers the changed blocks. Options like `-a`, `-v`, and `-z` modify other aspects of the transfer (like preserving permissions, providing verbose output, and compressing data), but the delta transfer is inherent to how `rsync` operates.

Correct answer: A permissive license (e.g., MIT, BSD)

Permissive licenses, such as the MIT, BSD, or Apache 2.0 licenses, have minimal restrictions on how the software can be used. They allow the code to be integrated into proprietary software without requiring the resulting work to also be open source. Their main condition is the preservation of the original copyright and license notices. A copyleft license like the GPL would require derivative works to also be released under the GPL.

Correct answer: Infrastructure as a Service (IaaS)

Infrastructure as a Service (IaaS) provides virtualized computing resources over the internet. It offers the highest level of control, as the organization is responsible for managing the operating system, applications, and middleware. This model is equivalent to having a virtual machine in the cloud, which perfectly matches the requirement for full control over the OS and software.

Correct answer: False

The statement is false. The core principle of a Zero Trust model is 'never trust, always verify.' It assumes that the internal network is no more secure than the external network. Every access request must be authenticated and authorized, regardless of whether it originates from inside or outside the network perimeter.

Correct answer: This represents a continuous integration (CI) and continuous deployment (CD) pipeline.

The diagram correctly illustrates a typical CI/CD pipeline. The Continuous Integration (CI) part includes compiling code and running tests upon commit. The Continuous Deployment (CD) part involves automatically packaging the application and deploying it to an environment like staging. This automated, sequential workflow is the foundation of CI/CD.