Using Firebase Email/Password login, what is the expected behavior if a user attempts to sign in with an email that is not registered?
Think about how Firebase handles sign-in attempts with unknown emails.
Firebase requires users to be registered before signing in. If the email is not found, it returns an error indicating the user does not exist.
In Firebase Realtime Database or Firestore, which security rule ensures that users can only read and write their own data after email/password login?
Consider how to restrict access to only the authenticated user's own data.
This rule checks that the user is authenticated and that their user ID matches the data's userId field, ensuring only owners access their data.
Which configuration snippet correctly enables email/password sign-in method in Firebase Authentication?
Think about where sign-in methods are enabled in Firebase.
Email/password sign-in is enabled via the Firebase Console under Authentication settings, not by code commands.
How does Firebase Authentication handle user passwords to keep them secure?
Consider industry best practices for password storage.
Firebase Authentication securely hashes and salts passwords internally, so developers never see raw passwords.
In Firebase Email/Password login, what is the best practice to protect against repeated failed login attempts?
Think about Firebase's native protections and monitoring tools.
Firebase Authentication includes built-in protections like rate limiting and provides monitoring tools to detect suspicious login attempts.