This same developer has noted that there is a risk that the app might not successfully find weather data for the user's location.  The likelihood of this happening is high, due to the apps architecture which attempts to locate data based on the user's exact location. The severity is medium, since the type of failure we're talking about results in no data be supplied to the app, but the app will still run and no personal data is breached. What response would be most appropriate?(1 point)ResponsesTransfer - tell the user they need to contact their mobile device's manufacturer because there might be a defectTransfer - tell the user they need to contact their mobile device's manufacturer because there might be a defectAccept - guess we just won't have data, except when we're in specific locationsAccept - guess we just won't have data, except when we're in specific locationsAvoid - employ your development team with the task of creating fallbacks, such as finding the nearest available data, if the app is unable to find weather data for the user's locationAvoid - employ your development team with the task of creating fallbacks, such as finding the nearest available data, if the app is unable to find weather data for the user's locationMitigate - create a way for the user to let the development team know there is an issue, then they can send the requested data to the user

1 answer

The most appropriate response would be:

Avoid - employ your development team with the task of creating fallbacks, such as finding the nearest available data, if the app is unable to find weather data for the user's location.

This approach proactively addresses the risk by improving the app's architecture to ensure that even if the app cannot find data for the user's exact location, it can still provide relevant information from nearby sources. This enhances user experience and addresses the high likelihood of failure without compromising the app's performance.