Form cover

Page 1 of 2

Hello Humanity — React SDK Quickstart Quiz

Section 1: Architecture and Setup

1. Why must the BrowserRouter component be the outermost layer, wrapping HumanityProvider?

*

1. Why must the BrowserRouter component be the outermost layer, wrapping HumanityProvider?

A

It's just a style convention with no functional effect.

B

It's required for React Strict Mode to detect hook errors.

C

The SDK uses internal routing for authentication callbacks, so it requires the router at the top level to function correctly.

D

HumanityProvider needs BrowserRouter to fetch environment variables.

2. Which environment should be selected in the Developer Portal when initially building and testing your application?

*

2. Which environment should be selected in the Developer Portal when initially building and testing your application?

A

Production

B

Sandbox

C

Staging

D

Mainnet

3. To ensure communication between your local dev server and the Developer Portal, which two settings must match exactly?

*

3. To ensure communication between your local dev server and the Developer Portal, which two settings must match exactly?

A

The API key and the Client Secret.

B

The Node.js version and the SDK version.

C

The port used by your local server (e.g., 3000) and the port defined in the Redirect URI in Developer Portal settings.

D

The domain name and the SSL certificate.

Section 2: Verification Workflow

4. What is the specific purpose of checking the "is human" credential preset?

*

4. What is the specific purpose of checking the "is human" credential preset?

A

To confirm the user has linked a crypto wallet.

B

To check whether the user has completed KYC document verification.

C

To verify users have biometric data (like a palm print) associated with their profile, proving they're a real human and not a bot or AI.

D

To confirm the user has verified their email address.

5. When implementing the useVerification hook, why check result.value === true rather than just checking if the result object exists?

*

5. When implementing the useVerification hook, why check result.value === true rather than just checking if the result object exists?

A

Because result will always be null regardless of pass/fail.

B

To avoid a TypeScript compilation error.

C

Checking only for the result object might just confirm the preset itself is valid; checking .value confirms the user actually passed verification.

D

Because .exists() is deprecated in the current SDK version.

6. Why is it important to handle a "loading" state when using hooks like useHumanity?

*

6. Why is it important to handle a "loading" state when using hooks like useHumanity?

A

The SDK initializes asynchronously, and failing to handle the loading state can cause a visual flicker in the UI.

B

It's only needed when using the Connect SDK, not the React SDK.

C

Without it, the hook throws an unhandled promise rejection.

D

Loading state is required to satisfy TypeScript's strict null checks.

Section 3: Testing Utilities

7. How can you test the full authentication and verification flow without using real biometric data?

*

7. How can you test the full authentication and verification flow without using real biometric data?

A

By using a shared test account provided by Humanity support.

B

By switching the SDK to "demo mode" in production.

C

By disabling verification checks in the SDK config.

D

By creating "mock credentials" (such as a mock palm print) in the sandbox environment via developer tools.

8. What is the function of the clearVerificationCache utility during testing?

*

8. What is the function of the clearVerificationCache utility during testing?

A

It resets the Developer Portal's redirect URI settings.

B

It logs the user out of their current session.

C

It clears the stored result so the hook queries the credential again for a fresh verification instead of returning a cached result.

D

It deletes the user's mock credentials permanently.