Idanwo ti o sopọ mọ itọsọna · Alabọde Ipele
Idanwo Awọn ikọlu Abẹrẹ kiakia
Review instruction trust boundaries and indirect injection, with tool containment, hierarchy training, task disruption, and multimodal input risks.
Ibeere 1 ti 8
Which trust failure can a prompt-injection attempt exploit?
Awotẹlẹ gbogbo ibeere8 ibeere
Awọn idahun ati awọn alaye han bi o ṣe n mu ibeere naa.
- Which trust failure can a prompt-injection attempt exploit?
- Adversarial instructions in task material being followed as authoritative commands
- A requirement that every model encrypt its entire context
- A guarantee that all models have administrator privileges
- A requirement that every model always obey every input
- Bawo ni abẹrẹ INDIRECT ṣe yatọ si abẹrẹ taara?
- O ṣiṣẹ nikan lori awọn awoṣe aworan
- O nilo iraye si ti ara si olupin naa
- Awọn ilana irira n gbe ni orisun ita ti awoṣe ka nigbamii, kii ṣe ninu ifiranṣẹ olumulo tirẹ
- O ti wa ni ošišẹ ti awọn Olùgbéejáde lori idi
- Which availability goal does the cited indirect-injection taxonomy include?
- Only stealing an entire training corpus in every attack
- Inhibiting useful responses or disrupting a search task
- Only changing a GPU’s physical memory size
- Only improving all authorized search results
- How can least-privilege tool permissions limit a successful injection’s consequences?
- They prove every allowed operation is harmless in every context
- They guarantee the model never proposes an injected action
- They remove the need for any output or action validation
- They restrict the operations and resources available to the workflow
- What behavior does the Instruction Hierarchy study aim to train?
- Sorting all retrieved words alphabetically
- Treating every webpage as more authoritative than the developer
- Following privileged instructions over conflicting lower-priority content
- Encrypting the model vocabulary with an image key
- Kini idi ti abẹrẹ kiakia di eewu diẹ sii bi awọn aṣoju AI ṣe gba awọn irinṣẹ?
- Aṣoju aṣiwere le ṣe awọn iṣe gidi bayi bi fifiranṣẹ imeeli, koodu ṣiṣiṣẹ, tabi data jijo
- Awọn aṣoju nṣiṣẹ diẹ sii laiyara pẹlu awọn irinṣẹ
- Awọn irinṣẹ jẹ ki awoṣe gbagbe ikẹkọ rẹ
- Irinṣẹ ė awọn perplexity awoṣe
- Why should a prompt-injection evaluation cover images when an application accepts multimodal input?
- Images guarantee that all instructions are trustworthy
- An image can contain only one numerical scalar
- Plain-text testing automatically covers every image input
- Adversarial instructions can be embedded in an image channel
- Why is merely quoting an attack instruction not enough to establish that an application was compromised?
- Every quoted string necessarily changes system permissions
- The text may be legitimate analysis material and may never be executed as an instruction
- An attacker must modify all original model weights first
- No authorized user can ever discuss a security attack