[&] What is a common indicator that a SOAP web service has hidden methods not listed in the WSDL?
- Common operations such as 'Get', 'Create', and 'Update' suggest additional methods.
- The web service openly lists every single operation.
- There are no hidden methods if the WSDL is comprehensive.
- All potential method names are revealed.

[&] What is the purpose of the SOAP action header in SOAP requests?
- It helps identify the intention of the SOAP request
- It compresses the SOAP body content
- It provides encryption for SOAP messages
- It improves the speed of the SOAP response

[&] How can a tester infer the existence of hidden SOAP operations?
- By ensuring all HTTP headers are encrypted
- Through contacting the web service owner
- By relying solely on WSDL documentation
- By guessing names based on visible operations

[&] What does a 200 status code indicate when invoking a hidden SOAP operation?
- The operation's parameters are incorrect but the method exists.
- All hidden methods are accessible without restrictions.
- The SOAP operation definitely exists and executed successfully.
- The SOAP action header was not necessary for this operation.

[&] Why is checking the WSDL important in identifying hidden SOAP methods?
- It guarantees discovering all hidden methods
- It ensures SOAP messages are always encrypted
- It may reveal method names and required parameters
- It provides authentication for accessing the endpoint

[&] What typically happens if a SOAP request is made to a non-existent method?
- The web service displays a user-friendly error page.
- The web service responds with a 500 status code.
- A successful 200 status code is returned.
- The request is ignored with no response.