Intelligent Agents Questions and Answers

Q: What is the contract net protocol?

The manager broadcasts a task announcement, interested agents submit bids, the manager awards the contract and the winner reports back, and any agent may act as manager for a subtask it cannot handle. It is one of the oldest and most durable coordination protocols. The other options describe legal agreements, shared contracts and resource markets. A protocol in which roles are assumed dynamically rather than fixed is what allows the same scheme to handle hierarchical task decomposition.

Q: Why does a distributed coordination protocol avoid a central planner?

Routing every decision through one component limits throughput, fails completely if that component fails, and requires global information that may not be available. Distributed protocols trade some optimality for robustness and scale. A central planner can compute optimal allocations given the information, which is precisely its advantage, and regulation is not the issue. Trading a guaranteed optimum for resilience and scale is a decision that depends on how likely failure is and how much optimality is worth.

Q: What is the frame of reference problem in observing an agent?

Simon's ant traces a complex path across a beach, but the complexity belongs to the terrain rather than to the ant, whose rules are simple, and the same caution applies to any behaviour attributed to an agent. Coordinate systems and relative motion are different senses of the phrase. Resisting the inference from complicated behaviour to a complicated mechanism is a discipline that saves both overestimating simple systems and underestimating the role of the environment.

Q: What does Simon's ant illustrate?

The ant's intricate path is explained by a few simple local rules interacting with an irregular beach, so the observed complexity is largely the environment's. It is the founding parable of behaviour based robotics and a standing caution against inferring mechanism from behaviour. Insect cognition, simulation fidelity and mapping are not the point. An argument that relocates the source of complexity from the agent to its surroundings changes what one expects to find inside.

Q: What is an agent's competence envelope?

Every agent works well within some range of conditions and degrades outside it, and knowing where that boundary lies matters as much as knowing how it performs inside. An agent that recognises when it is outside its envelope, and says so, is far safer than one that continues confidently. Reach, design intent and service life are different notions. Characterising the boundary rather than only the centre of an operating range is what makes a deployment trustworthy.

Q: Why should an agent detect when it is outside its competence?

An agent that knows it is uncertain can stop, ask, or take a conservative action, whereas one that does not continues to act confidently on unreliable conclusions. Calibrated uncertainty and out of distribution detection are the technical means. Automatic expansion, logging and measurability are separate matters. Knowing what one does not know is a capability rather than an absence of one, and designing for it explicitly is what separates a cautious system from a brittle one.

Q: What is the practical value of the agent framework to a working engineer?

The framework contributes vocabulary and a checklist rather than algorithms, and its value lies in the discipline of settling the performance measure, environment and interface first. Algorithms come from the subfields, no framework guarantees behaviour, and domain understanding remains essential. A conceptual framework whose main contribution is a well ordered set of questions is less exciting than one that supplies answers, and frequently more useful.

Q: What single mistake does the agent framework most often prevent?

By requiring the performance measure to be written down first, and written in terms of outcomes rather than behaviour, the framework confronts the designer with the objective before any code exists. That is where the most expensive errors are made and the hardest to detect afterwards. Algorithm efficiency, language choice and data volume are recoverable mistakes. An error in the specification is reproduced faithfully by every subsequent stage, which is why catching it first matters so much.

Q: Why is the performance measure written in terms of outcomes rather than actions?

Rewarding an outcome states what is wanted and lets the agent discover how to achieve it, which is the whole advantage of a declarative specification. Prescribing actions freezes the designer's assumptions into the system. Measurability often runs the other way, actions are usually observable, and enumeration is a practical rather than a principled objection. Saying what rather than how is a principle borrowed from declarative programming and it applies here with the same force.

101.

What is the contract net protocol?

A.Agents sign binding contracts before a system is deployed
B.A network of agents shares a single contract for all tasks
C.Agents negotiate the price of computing resources continuously
D.A manager announces a task and agents bid to perform it

Answer: D

The manager broadcasts a task announcement, interested agents submit bids, the manager awards the contract and the winner reports back, and any agent may act as manager for a subtask it cannot handle. It is one of the oldest and most durable coordination protocols. The other options describe legal agreements, shared contracts and resource markets. A protocol in which roles are assumed dynamically rather than fixed is what allows the same scheme to handle hierarchical task decomposition.

Discuss in Forum

102.

Why does a distributed coordination protocol avoid a central planner?

A.A central planner is a bottleneck and a single point of failure
B.Central planners cannot compute optimal allocations at all
C.Distributed protocols always produce better allocations
D.Regulations forbid central control of autonomous systems

Answer: A

Routing every decision through one component limits throughput, fails completely if that component fails, and requires global information that may not be available. Distributed protocols trade some optimality for robustness and scale. A central planner can compute optimal allocations given the information, which is precisely its advantage, and regulation is not the issue. Trading a guaranteed optimum for resilience and scale is a decision that depends on how likely failure is and how much optimality is worth.

Discuss in Forum

103.

What is the frame of reference problem in observing an agent?

A.The agent's coordinate system differs from the environment's
B.Behaviour described from outside may not reflect internal complexity
C.Agents cannot observe their own position within the environment
D.Different observers measure the agent's speed differently

Answer: B

Simon's ant traces a complex path across a beach, but the complexity belongs to the terrain rather than to the ant, whose rules are simple, and the same caution applies to any behaviour attributed to an agent. Coordinate systems and relative motion are different senses of the phrase. Resisting the inference from complicated behaviour to a complicated mechanism is a discipline that saves both overestimating simple systems and underestimating the role of the environment.

Discuss in Forum

104.

What does Simon's ant illustrate?

A.Simulated agents behave differently from physical ones
B.Path planning requires a detailed map of the terrain
C.Complex behaviour can arise from simple rules in a complex environment
D.Insects are capable of sophisticated internal reasoning

Answer: C

The ant's intricate path is explained by a few simple local rules interacting with an irregular beach, so the observed complexity is largely the environment's. It is the founding parable of behaviour based robotics and a standing caution against inferring mechanism from behaviour. Insect cognition, simulation fidelity and mapping are not the point. An argument that relocates the source of complexity from the agent to its surroundings changes what one expects to find inside.

Discuss in Forum

105.

What is an agent's competence envelope?

A.The physical volume within which its actuators can reach
B.The set of tasks it was originally designed to perform
C.The period over which its performance remains within specification
D.The range of situations in which it performs acceptably

Answer: D

Every agent works well within some range of conditions and degrades outside it, and knowing where that boundary lies matters as much as knowing how it performs inside. An agent that recognises when it is outside its envelope, and says so, is far safer than one that continues confidently. Reach, design intent and service life are different notions. Characterising the boundary rather than only the centre of an operating range is what makes a deployment trustworthy.

Discuss in Forum

106.

Why should an agent detect when it is outside its competence?

A.It can then defer to a human or fall back to a safe behaviour
B.Detection allows the agent to expand its envelope automatically
C.Regulations require every agent to log its operating conditions
D.The agent's performance measure cannot be computed outside it

Answer: A

An agent that knows it is uncertain can stop, ask, or take a conservative action, whereas one that does not continues to act confidently on unreliable conclusions. Calibrated uncertainty and out of distribution detection are the technical means. Automatic expansion, logging and measurability are separate matters. Knowing what one does not know is a capability rather than an absence of one, and designing for it explicitly is what separates a cautious system from a brittle one.

Discuss in Forum

107.

What is the practical value of the agent framework to a working engineer?

A.It removes the need to understand the application domain
B.It forces the problem to be specified before a solution is chosen
C.It supplies algorithms that solve most practical problems directly
D.It guarantees that the resulting system will behave rationally

Answer: B

The framework contributes vocabulary and a checklist rather than algorithms, and its value lies in the discipline of settling the performance measure, environment and interface first. Algorithms come from the subfields, no framework guarantees behaviour, and domain understanding remains essential. A conceptual framework whose main contribution is a well ordered set of questions is less exciting than one that supplies answers, and frequently more useful.

Discuss in Forum

108.

What single mistake does the agent framework most often prevent?

A.Implementing a system in an unsuitable programming language
B.Failing to collect enough training data before deployment
C.Optimising something other than what was actually wanted
D.Choosing an inefficient algorithm for a well specified problem

Answer: C

By requiring the performance measure to be written down first, and written in terms of outcomes rather than behaviour, the framework confronts the designer with the objective before any code exists. That is where the most expensive errors are made and the hardest to detect afterwards. Algorithm efficiency, language choice and data volume are recoverable mistakes. An error in the specification is reproduced faithfully by every subsequent stage, which is why catching it first matters so much.

Discuss in Forum

109.

Why is the performance measure written in terms of outcomes rather than actions?

A.Outcomes are always easier to measure than the actions taken
B.Actions cannot be observed reliably once the agent is deployed
C.Specifying actions would require a complete list of every situation
D.It leaves the agent free to find a better method than the designer knew

Answer: D

Rewarding an outcome states what is wanted and lets the agent discover how to achieve it, which is the whole advantage of a declarative specification. Prescribing actions freezes the designer's assumptions into the system. Measurability often runs the other way, actions are usually observable, and enumeration is a practical rather than a principled objection. Saying what rather than how is a principle borrowed from declarative programming and it applies here with the same force.

Discuss in Forum

Loading…

Topics

Other Subjects

Tags: Intelligent Agents Questions and Answers || Intelligent Agents MCQ Questions and Answers || Intelligent Agents GK Questions and Answers || Intelligent Agents GK MCQ Questions || Intelligent Agents Multiple Choice Questions and Answers || Intelligent Agents GK || GK on Intelligent Agents || Artificial Intelligence Questions and Answers || Artificial Intelligence MCQ Questions and Answers || Artificial Intelligence GK Questions and Answers || GK on Artificial Intelligence

Intelligent Agents Questions and Answers

Topics

Other Subjects

About Us

Stay informed about all important Dates & Notifications