Q1: What Jmeter modes exist?
- [ ] CLI mode
- [ ] CLD mode > I made this one up
- [ ] Server mode
- [ ] Debug mode > Debug is a config and not really a mod
Q2: Where can I change the amount of RAM allocated to JMeter
- [ ] With a CLI flag
- [ ] In the jmeter.bat file for unix
- [ ] In the buffer
- [ ] In the shell file for linux
Q3: Why would you add or remove things from JMeter scripts in GUI mode... But for the actual load generating go over to CLI mode
- [ ] Because this allows us to type a command instead of clicking everywhere which saves vital milliseconds
- [ ] Because GUIs take up resources the system might need during load generation
- [ ] Because CLI mode is much easier to integrate into the build pipelines for automated performance testing
Q4: What is the use of the flag -n with the JMeter CLI interface?
- [ ] Makes Jmeter run in CLI mode
- [ ] Optional: set up a proxy such as burp suite or any other
- [ ] Optional: set up a proxy such as OWASP ZAP or any other
- [ ] Points jmeter to the location of the script to run
Q5: What flag needs to be selected in the JMeter CLI mode to enable a proxy