← Back to companies
[ OK ] Loaded —
[ INFO ]
$ cd
$ ls -lt
01
02
03
04
05
$ ls -lt
01
02
03
04
05
user@intervues:~/$
No specific PayPal interview question titled "Spring Boot Output / HTTP Response Codes" with exact tags (Backend, Spring Boot, HTTP) appears in comprehensive web searches across coding platforms, interview prep sites, LeetCode, Glassdoor, GitHub repos, or PayPal-specific OA discussions.[1][2][3][5][6][9]
Searches suggest this refers to common Spring Boot tasks involving ResponseEntity for custom HTTP status codes in REST APIs, often tested in backend interviews.[5][1]
Typical problem: Build endpoints returning specific codes like 200 (OK), 201 (Created), 400 (Bad Request), 404 (Not Found), or 500 (Internal Error) based on logic, with JSON outputs.
return ResponseEntity.ok("Resource found"); → HTTP 200.[1][5]return ResponseEntity.status(HttpStatus.CREATED).body(newResource); → HTTP 201.[1]return ResponseEntity.notFound().build(); → HTTP 404.[5][1]return ResponseEntity.badRequest().body("Invalid input"); → HTTP 400.[5]No full problem statement, input/output examples, or constraints match the exact title; it may be internal/proprietary or from a private OA not publicly indexed.[6][9]