Q1: What Jmeter modes exist?

• [ ] CLI mode > CLI mode does exist ✅
• [ ] CLD mode > I made this one up ❌
• [ ] Server mode > Jmeter can be run as a server that is controlled by the agent ✅
• [ ] Debug mode > Debug is a config and not really a mode❌\

Q2: Where can I change the amount of RAM allocated to JMeter

• [ ] With a CLI flag > We can pass along a parameters when starting jmeter via the command line to change the allocated amount of RAM✅
• [ ] In the jmeter.bat file for unix > Unix can not start bat files by default❌
• [ ] In the buffer > You can not control this in Java which is what Jmeter is based upon❌
• [ ] In the shell file for linux > It can be changed in the startup sh file ✅

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 > The fact we need to click around has nothing to do with running Jmeter in headless mode❌
• [ ] Because GUIs take up resources the system might need during load generation > These resources can substantially slow down the actual test✅
• [ ] Because CLI mode is much easier to integrate into the build pipelines for automated performance testing > We need to be able to run Jmeter with a command so we can integrate it with our build pipelines✅

Q4: What is the use of the flag -n with the JMeter CLI interface?

• [ ] Makes Jmeter run in headless mode > Via the CLI we can start JMeter in headless mode so it will use up less resources✅
• [ ] This flag is Optional: set up a proxy such as burp suite or any other > No that would be the -P flag for port and -H flag for the server❌
• [ ] Optional: set up a proxy such as OWASP ZAP or any other > No that would be the -P flag for port and -H flag for the server❌
• [ ] Points jmeter to the location of the script to run > That would be the -t flag ❌

Q5: What flag needs to be selected in the JMeter CLI mode to enable a proxy