Securing Serverless Functions GPCS Practice Questions (Page 9)

Questions 41–45

1. 41foundation · easy

   What is a key challenge when performing forensic analysis on serverless functions?

   • AThe function cannot be invoked after an incident, so no data can be collected
   • BThe cloud provider does not retain any logs for serverless functions
   • CThe ephemeral nature of the execution environment makes it difficult to capture memory dumps or disk images
   • DThe function's code is always encrypted and cannot be analyzed
   Reveal Solution Discussion Select an answer first
2. 42application · medium

   A team is developing a serverless function that uses several open-source npm packages. The security team wants to reduce the risk of supply chain attacks before the function is deployed. Which approach is most effective?

   • AUse the latest versions of all dependencies and rely on the package registry to remove malicious packages.
   • BAvoid using any third-party packages and write all functionality from scratch.
   • CCopy the source code of all dependencies into the function's deployment package and review it manually.
   • DPin dependencies to exact versions and run a vulnerability scanner in the CI/CD pipeline.
   Reveal Solution Discussion Select an answer first
4. 43foundation · easy

   How should a serverless function retrieve a database password at runtime?

   • AHardcode the password in the function code for simplicity
   • BAsk the user to provide the password in each request
   • CRetrieve it from a dedicated secrets management service using the function's IAM role
   • DStore it in a plain text file in the function's deployment package
   Reveal Solution Discussion Select an answer first
5. 44foundation · easy

   What is the purpose of enabling monitoring and alerting for serverless functions?

   • ATo automatically change the function's code when errors occur
   • BTo prevent the function from being invoked by unauthorized users
   • CTo encrypt the function's data at rest
   • DTo track performance and security metrics and notify administrators of anomalies
   Reveal Solution Discussion Select an answer first
6. 45application · medium

   A developer wrote an Azure Function that accepts a JSON payload from an HTTP trigger, extracts a 'name' field, and inserts it into a SQL database using parameterized queries. The function also logs the raw payload to Application Insights. A security review flags a risk. What should the developer change?

   • AKeep the logging as-is but add a try-catch block to handle any SQL exceptions.
   • BRemove parameterized queries and use string concatenation to build the SQL statement, then validate the input.
   • CChange the function to use a queue trigger instead of an HTTP trigger to avoid input validation.
   • DAdd input validation to ensure the 'name' field is a string of expected length and character set, and redact or truncate the raw payload before logging.
   Reveal Solution Discussion Select an answer first