You have just checked the balance in your bank account by logging into your bank's Web site. Which protocol was most likely used for the transmission of your information?

The correct answer is B. HTTPS. HTTPS (HyperText Transfer Protocol Secure) is the standard protocol for secure web communication - when you log into a banking site, your browser establishes an encrypted HTTPS connection (port 443) to protect credentials and account data in transit. Why the distractors are…

Internet Basics and Web Browsing

Question

You have just checked the balance in your bank account by logging into your bank’s Web site. Which protocol was most likely used for the transmission of your information?

Options

AIMAPS
BHTTPS
CPOP
DFTPS

How the community answered

(34 responses)

B
94% (32)
C
3% (1)
D
3% (1)

Explanation

HTTPS (HyperText Transfer Protocol Secure) is the standard protocol for secure web communication - when you log into a banking site, your browser establishes an encrypted HTTPS connection (port 443) to protect credentials and account data in transit.

Why the distractors are wrong:

IMAPS (IMAP Secure) is for retrieving email over an encrypted connection - not web browsing.
POP (Post Office Protocol) also handles email retrieval, and the base version isn't even encrypted.
FTPS (FTP Secure) is for encrypted file transfers between systems, not website logins.

Memory tip: The "S" in HTTPS stands for Secure - any time you see a padlock icon in your browser's address bar, that's HTTPS at work. Bank sites, shopping carts, and login pages all require it. If the question involves a browser and sensitive data, the answer is almost always HTTPS.

Topics

#HTTPS#SSL/TLS encryption#Secure web transmission#Web protocols

Community Discussion

Mateus R.Jun 27, 2026

Think of logging into your bank's website like walking into a vault through a locked glass tunnel where nobody outside can see or touch what passes between you and the teller, and that locked tunnel is exactly what HTTPS provides by wrapping your web traffic in TLS encryption. The answer is B, HTTPS, because the other options handle email (IMAPS, POP) and file transfers (FTPS), none of which are the protocol your browser uses to securely load and submit web pages.

Mei-Ling H.Jun 28, 2026

HTTPS is right but worth noting the tunnel metaphor slightly oversimplifies it, because TLS also handles server authentication via the certificate, so you are not just hiding the contents but also verifying you are actually talking to your real bank and not an impostor.

Nina C.Jun 27, 2026

Okay so before I just say "B and done," I want to make sure I understand why the others are wrong, because FTPS actually tripped me up at first since it does encrypt, just like HTTPS does. IMAPS and POP are both email protocols, so those are out immediately, nothing to do with a web browser or a bank login page. FTPS is the one that made me pause, because it is encrypted FTP and people do use it to transfer files securely, but your bank is not sending you a file, you are logging into a website through a browser. HTTPS is the protocol your browser uses specifically for secure web page transmission, which is exactly what happens when you see that padlock and type in your credentials on a login page. So even though FTPS encrypts data in transit the same way, the question says "Web site" and that points directly to HTTP with the S for SSL/TLS on top, which is HTTPS, answer B.

Mei-Ling H.Jun 29, 2026

Nina, good breakdown, just one thing to add: "SSL/TLS on top" is more accurate to say TLS on top, since SSL is deprecated and modern HTTPS uses TLS, which matters if your exam uses that wording.

Mei-Ling H.Jun 27, 2026

The word "Web site" is doing a lot of work in this question and I think some people skip right past it. IMAPS and POP are both email protocols, so they drop out fast, and FTPS is for file transfer, not browsing. The secure web protocol is the one that puts a padlock in your browser and uses port 443, so the answer points clearly to B. My study guide says HTTPS wraps HTTP inside TLS, which handles both encryption and authentication for the server, and that is exactly what a banking login page needs. Here is what I am still fuzzy on though: if the bank also sends a confirmation email after you log in, would that email leg of the process use IMAPS or HTTPS for the transmission, and does the exam ever ask you to identify which protocol covers which specific segment of a multi-step transaction like that?

Quincy P.Jun 27, 2026

IMAPS covers the delivery of that confirmation email to your inbox (client-to-mail-server retrieval, port 993), while HTTPS would only apply if you clicked a link in that email and opened it in a browser, and yes, the CIW exam does test exactly this kind of segment-level protocol identification so knowing the handoff point between each layer is worth drilling.

Ingrid P.Jun 27, 2026

I kept second-guessing myself on this one and almost marked FTPS because I had just been drilling file-transfer protocols and my brain was primed to see anything with encryption as an FTP variant. What snapped me out of it was thinking about what actually happens when you click "Log In" on a bank site, your browser is making HTTP requests to a web server and the padlock in the address bar is TLS wrapping those requests, which is exactly what HTTPS is. IMAPS and POP are email retrieval protocols, completely wrong domain, and plain POP has zero encryption anyway so that is a trap option designed to catch people who just scan for familiar names. The card I made for this one has the cue "browser plus padlock equals HTTPS" and I review it at a 4-day interval now because web-layer protocol questions keep coming up in different surface forms on this exam.

Quincy P.Jun 22, 2026

FTPS is a trap here, but bank login pages run HTTPS, full stop.

Full 1D0-61A Practice