Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Q-35 Mock Exam: Conflict in Runtime Configuration vs Robustness #106

Open
g1raffi opened this issue Jun 25, 2021 · 1 comment
Open

Q-35 Mock Exam: Conflict in Runtime Configuration vs Robustness #106

g1raffi opened this issue Jun 25, 2021 · 1 comment

Comments

@g1raffi
Copy link

g1raffi commented Jun 25, 2021

Hey guys,
In a new world where runtime configuration is key to every system, I think it is an outdated opinion to generally say that Runtime Configuration vs Robustness stands in conflict.

Regards,
Raffael

@g1raffi g1raffi changed the title Q35 Mock Exam: Conflict in Runtime Configuration vs Robustness Q-35 Mock Exam: Conflict in Runtime Configuration vs Robustness Jun 25, 2021
@alxlo
Copy link
Contributor

alxlo commented Jun 25, 2021

  • "key to every system" is definitely not true. Consider systems or components outside the scope of your daily work.
  • The question leaves it open whether we talk about components (e.g. libraries) or whole systems
  • even it would be "key to every system", that doesn't change the fact that adding (possibly complex) configuration functionality to a system/component increases the chance of errors, creates attack vectors and makes testing harder which in turn leads to reduced robustness

I would rather argue about option d) because legal compliance issues (data retention laws, access for law enforcement) can indeed compromise security. However, I would not like to over-fit the mock exam. IMHO there should be answers in here that are "not perfect" to make people more cautious for pedagogical reasons.

If this would be a real exam question I would be unhappy about this and propose to turn it into a pick question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants