MCQs on Crate Development and Publishing | Rust

Rust provides a robust ecosystem for package management and distribution through crates. This set of 30 multiple-choice questions covers important topics such as organizing and structuring crates, managing dependencies in Cargo.toml, writing documentation, and publishing crates to crates.io. These practices help developers create well-structured libraries and applications in Rust.

---

MCQs on Crate Development and Publishing in Rust

Structuring and Organizing a Rust Crate

1. What is the primary unit of code reuse in Rust?
   • A) Package
   • B) Module
   • C) Crate
   • D) Library
2. What file is used to define a crate’s metadata in Rust?
   • A) Cargo.toml
   • B) Rust.toml
   • C) manifest.toml
   • D) crate.toml
3. Where should the source code of a Rust crate be placed?
   • A) Inside the src directory
   • B) Inside the bin directory
   • C) Inside the lib directory
   • D) Inside the doc directory
4. What is the default entry point for a binary crate in Rust?
   • A) main.rs
   • B) lib.rs
   • C) index.rs
   • D) start.rs
5. Which of the following is a valid directory structure for a library crate in Rust?
   • A) src/lib.rs
   • B) src/main.rs
   • C) lib.rs/src
   • D) bin/lib.rs
6. What is the purpose of the lib.rs file in a Rust crate?
   • A) It contains the main function for a binary crate
   • B) It contains the library code for the crate
   • C) It configures the Cargo.toml file
   • D) It stores external dependencies for the crate
7. Which file would you use to specify the name and version of your crate?
   • A) Cargo.toml
   • B) main.rs
   • C) manifest.rs
   • D) crate.json
8. How are multiple crates related in a Rust project?
   • A) Through the use of dependencies specified in Cargo.toml
   • B) Through direct file imports
   • C) By using the use keyword
   • D) Rust does not support multiple crates in a project
9. What directory should contain your Cargo.toml file in a multi-crate project?
   • A) Root of the project
   • B) Inside the src directory
   • C) Inside the lib directory
   • D) Inside the bin directory
10. How does Cargo know which files to include in the crate?
    • A) Based on the Cargo.toml configuration
    • B) By scanning the entire directory
    • C) Through a configuration file called files.toml
    • D) By reading all .rs files in the project directory

Writing Documentation for Crates

11. What syntax is used to document a Rust crate or module?

• A) ///
• B) //
• C) /* */
• D) --

12. Where do you write the documentation for a function in Rust?

• A) Just before the function signature
• B) Inside the function body
• C) At the end of the function
• D) After the function return statement

13. Which command generates documentation for a Rust crate?

• A) cargo build
• B) cargo test
• C) cargo doc
• D) cargo publish

14. How do you link documentation to another crate in Rust?

• A) By using #[link]
• B) By using /// with the crate URL
• C) By adding a dependency in Cargo.toml
• D) By importing the crate using use

15. What should the first line of documentation for a function or crate contain?

• A) A description of the function’s parameters
• B) A summary of what the function or crate does
• C) The expected return value
• D) An example of how to use the function

16. How can you generate example code for a crate in Rust documentation?

• A) By using /// followed by example code blocks
• B) By using cargo example
• C) By adding example files in the src folder
• D) By writing code comments

17. What is the purpose of doc attributes in Rust?

• A) To define dependencies for the crate
• B) To add links to external documentation
• C) To generate HTML documentation from comments
• D) To optimize the crate’s performance

18. What format is used to write Rust crate documentation?

• A) Markdown
• B) LaTeX
• C) HTML
• D) JSON

19. How do you include external documentation links within your Rust crate?

• A) By using the #[doc] attribute with a URL
• B) By writing them in Markdown format
• C) By using use keyword for external links
• D) By adding them in the Cargo.toml file

20. What does the cargo doc --open command do?

• A) It opens the crate documentation in a web browser
• B) It builds the crate documentation without opening it
• C) It publishes the crate to crates.io
• D) It tests the crate’s documentation for errors

Managing Dependencies in Cargo.toml

21. How are external dependencies specified in a Cargo.toml file?

• A) Under the [dependencies] section
• B) In the src directory
• C) In a dependencies.rs file
• D) In the Cargo.lock file

22. What is the correct format for specifying the version of a dependency in Cargo.toml?

• A) name = "1.0.0"
• B) name = [1.0.0]
• C) name = 1.0.0
• D) name = { version = "1.0.0" }

23. Which command installs dependencies listed in the Cargo.toml file?

• A) cargo install
• B) cargo build
• C) cargo update
• D) cargo fetch

24. What is the purpose of the Cargo.lock file?

• A) To lock the dependencies to specific versions
• B) To store the source code of dependencies
• C) To document the crate’s version
• D) To store metadata about the crate

25. How can you update all dependencies to the latest compatible versions?

• A) cargo update
• B) cargo upgrade
• C) cargo install
• D) cargo build

26. What is the purpose of the [dev-dependencies] section in Cargo.toml?

• A) To specify dependencies used only for testing and development
• B) To specify production dependencies
• C) To list external libraries for deployment
• D) To define dependencies required for runtime

27. Can you specify optional dependencies in Cargo.toml?

• A) Yes, by using the [optional] section
• B) Yes, by using the [dependencies] section with optional = true
• C) No, dependencies must always be required
• D) No, optional dependencies are not supported

28. How do you add a dependency from a local directory in Cargo.toml?

• A) By using the path attribute
• B) By using the local attribute
• C) By adding it to the [local-dependencies] section
• D) By importing it directly in the src directory

29. How are features handled in Cargo.toml?

• A) Using the [features] section to define optional functionality
• B) Using the [dev-features] section
• C) By specifying features in the Cargo.lock file
• D) By importing them into the main crate file

30. Which command checks for dependency updates and their compatibility in your crate?

• A) cargo check
• B) cargo verify
• C) cargo update
• D) cargo audit

---

Answers

Qno	Answer
1	C) Crate
2	A) Cargo.toml
3	A) Inside the src directory
4	A) main.rs
5	A) src/lib.rs
6	B) It contains the library code for the crate
7	A) Cargo.toml
8	A) Through the use of dependencies specified in Cargo.toml
9	A) Root of the project
10	A) Based on the Cargo.toml configuration
11	A) ///
12	A) Just before the function signature
13	C) cargo doc
14	C) By adding a dependency in Cargo.toml
15	B) A summary of what the function or crate does
16	A) By using /// followed by example code blocks
17	C) To generate HTML documentation from comments
18	A) Markdown
19	A) By using the #[doc] attribute with a URL
20	A) It opens the crate documentation in a web browser
21	A) Under the [dependencies] section
22	D) name = { version = "1.0.0" }
23	B) cargo build
24	A) To lock the dependencies to specific versions
25	A) cargo update
26	A) To specify dependencies used only for testing and development
27	B) Yes, by using the [dependencies] section with optional = true
28	A) By using the path attribute
29	A) Using the [features] section to define optional functionality
30	C) cargo update