PSEB SS Fundamentals of E-Business common mistakes
PSEB SS Fundamentals of E-Business · Understand the traps and how to avoid them.
Treating 'e-business' and 'e-commerce' as interchangeable words and choosing whichever option sounds broader, without checking whether the option describes internal process integration or a buy/sell transaction.
The two terms appear together in almost every introductory chapter, and candidates memorise a one-line gloss ('e-commerce is buying and selling online') without the distinction that e-business also covers internal processes such as supply-chain, HR, and customer-service integration. Under time pressure the broader-sounding option wins by instinct.
What to do instead
Before answering, ask one test question of each option: does it involve an exchange of money or title between parties (commerce), or does it describe an internal or inter-firm process enabled by networks (business)? Build a two-column list from your own notes with five examples per column and rehearse it until the classification is automatic.
Mixing up the direction of B2B, B2C, C2B, and B2G transactions, especially when the question describes who initiates, who pays, and who delivers.
Candidates learn the labels as acronyms and match on the party that appears first in the sentence rather than on the flow of value. Questions that describe a consumer posting a price and firms bidding for it are commonly mislabelled as B2C because a consumer appears in the scenario.
What to do instead
For every scenario, write three short tags: seller, buyer, payer. The model is named from the two parties in the transaction, with the seller or initiator first in the standard convention used in your course material. Practise with ten short scenarios and label each from the tags, not from the wording.
Selecting a revenue model (subscription, advertising, transaction fee, freemium) based on the industry rather than on where the money actually comes from in the described case.
Candidates pattern-match industries to familiar companies, so any media example gets labelled advertising and any software example gets labelled subscription, even when the stem describes commission on completed sales or a one-off licence.
What to do instead
Answer the question 'who pays, for what, and how often?' in one sentence before looking at the options. If the payer is an advertiser, it is advertising; if the payer is the transacting party and the amount scales with volume, it is a transaction fee; if payment recurs for continued access, it is subscription. Match the sentence to the option, not the industry to the option.
Confusing an e-marketplace with an e-procurement or e-distribution arrangement, or confusing a horizontal exchange with a vertical one, when the stem names the participants and the goods traded.
The terms overlap in ordinary speech, and candidates remember the definitions as lists rather than as participant structures. Horizontal versus vertical is often recalled as 'size of company' rather than 'scope of goods or industry served'.
What to do instead
Redraw each model as a simple diagram showing who connects to whom and what is exchanged. For horizontal versus vertical, anchor on the goods: many industries buying the same category (office supplies, travel) is horizontal; one industry's specialised inputs is vertical. Redo the diagram from memory before the exam.
Treating the value chain as a list to memorise and then failing application questions that ask which primary or support activity a described task belongs to.
Primary and support activities are learned as names in sequence, so candidates cannot place a concrete task such as inbound logistics, outbound logistics, or procurement into the right category when the stem describes the task rather than naming it.
What to do instead
Learn the value chain as two questions: does this activity physically move or transform the product toward the customer (primary), or does it enable the whole chain (support)? Note the classic trap that procurement is a support activity even though it deals with inputs. Classify ten described tasks into primary or support and check each against the definition.
Answering e-payment questions by picking the most familiar payment instrument rather than the one matching the described properties such as irreversibility, anonymity, prepaid value, or settlement timing.
Payment instruments are studied as a list of examples, so candidates match on brand familiarity and ignore the property the stem is testing. Questions about stored-value cards, credit transfers, and digital wallets turn on these properties, not on which is most used.
What to do instead
Build a comparison table with columns for who bears credit risk, whether payment is prepaid or postpaid, whether the payer is identified, and when funds settle. Fill it from your course notes and answer property questions by eliminating options that contradict a stated property.
Confusing security goals with security mechanisms, for example naming encryption when the question asks for the property being protected, or naming a firewall when the question asks for the control objective.
Textbooks present goals (confidentiality, integrity, authentication, non-repudiation, availability) next to the technologies that deliver them. Candidates revise the technologies more heavily because they are concrete, then misread the question's subject.
What to do instead
Practise rewriting every question into 'asks for: goal or mechanism?' before reading options. Learn one mechanism per goal and one goal per mechanism, and note that digital signatures support integrity, authentication, and non-repudiation together while encryption alone supports confidentiality.
Misreading the direction of a question about SSL/TLS or SET, or about which party holds which key, and choosing an option that is technically true but answers the opposite direction.
Public-key material is dense, and candidates learn phrases such as 'encrypted with the sender's private key' without tracking who is sending, who is receiving, and what the purpose of the operation is. Direction errors survive revision because the phrase itself sounds correct.
What to do instead
For every cryptography item, write the sender, the receiver, and the purpose on the page before evaluating options. Then apply the rule that signing uses the sender's private key and confidentiality uses the receiver's public key. Check each option against the written roles rather than against the phrase.
Choosing the most advanced-sounding technology or the most recent-sounding option in questions about infrastructure, middleware, or architecture, instead of the option that satisfies the stated requirement.
Candidates without hands-on experience rank options by apparent sophistication. Stems that specify constraints such as existing legacy systems, low bandwidth, or a fixed budget are designed to make the modest option correct.
What to do instead
Underline the constraint words in the stem (legacy, low cost, intermittent connectivity, existing standards) and eliminate any option that violates a constraint, even if it is otherwise attractive. Answer from requirements, not from prestige.
Ignoring the legal and regulatory layer, or applying a single country's rules to every scenario, when the question concerns contracts, data protection, consumer protection, or taxation of online sales.
These topics feel peripheral next to technology and are revised last, so candidates rely on general impressions. They then pick an option that sounds fair rather than the one matching the principle the course teaches, such as when a contract is formed or which jurisdiction's rules apply.
What to do instead
Make a short list of the legal principles in your syllabus with one scenario each: offer and acceptance online, electronic signature validity, data-subject rights, and cross-border tax obligations. For each item, identify which principle is being tested before reading the options, and choose the option that states the principle rather than the fairest-sounding outcome.