Free LPI 702-100 Actual Exam Questions - Question 8 Discussion

C. You can definitely set build flags and enable features only at compile time, which you just can’t mess with in a pre-built binary. That’s the main advantage here.

It’s C as well. Another way to see it: when you compile from source, you can enable or disable features that are hardcoded into the app, which you simply can’t do with a binary. D doesn’t hold up since binaries are fixed in what they include or exclude at compile time, so they don’t really offer more options than source builds—just runtime settings, which aren’t the same thing.

It’s C for me. Compiling lets you set build options that stick, while binaries only let you change stuff at runtime, not the actual build settings. That’s a clear difference.

A says compiling is faster, but that feels off since compiling usually takes longer than installing.

Yeah, C makes sense since compile-time options can enable or disable features permanently, unlike runtime settings. That’s a clear difference from pre-compiled binaries which have fixed options. So I’d go with C.

C, since compile-time options can lock in features you can’t tweak afterwards.

Maybe C, since compile-time options often fix features you can't change later.

Makes sense to focus on build-time customization here. I think C’s the best choice because you can enable or disable features during compile that aren’t adjustable at runtime.

C/D? D seems wrong because pre-compiled binaries are usually fixed in options. C fits since build-time flags affect the final app in ways you can’t tweak later. That’s a solid distinction.

C looks right to me, since compiling lets you set build-time options you can't change later. The others seem off or too general.