First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Architect Fundamentals and the CTA Journey
In the CTA Awareness model, what does the abbreviation CTA stand for?
- Certified Technical Architect Correct answer.
- Certified Testing Analyst
- Customer Transformation Advisor
- Cloud Technology Associate
Explanation
CTA is the Certified Technical Architect credential, and the Awareness exam covers the fundamentals a candidate needs before pursuing deeper architect study. The other expansions describe unrelated roles or programs.
Question 2Architect Fundamentals and the CTA Journey
A candidate asks what the Awareness level of the CTA journey is designed to provide. Which description fits best?
- Foundational knowledge of architect concepts and the certification path Correct answer.
- Hands-on build experience with production deployments
- Full mastery of every architect domain
- Advanced peer review of solution designs
Explanation
Awareness is the entry point of the CTA journey: it introduces core architect concepts, terminology, and the path ahead rather than demanding production experience or design mastery. Deeper levels build the practical and review skills.
Question 3Architect Fundamentals and the CTA Journey
Which statement best describes the role of an architect in the CTA journey?
- An architect exclusively manages project budgets and staffing
- An architect only writes code for individual features
- An architect translates requirements into a coherent solution design and guides its realization Correct answer.
- An architect limits work to operating production servers
Explanation
Architects sit between business requirements and technical delivery, shaping a coherent design and guiding teams to realize it. Coding features, budget management, and server operations are narrower roles that an architect may influence but does not own.
Question 4Architect Fundamentals and the CTA Journey
During a discovery workshop, an architect documents who uses the system, what they need to accomplish, and why it matters. Which architect fundamental is being practiced?
- Incident triage
- Capacity planning
- Deployment automation
- Requirements gathering Correct answer.
Explanation
Capturing users, their goals, and the business rationale is requirements gathering, the foundation for every later design decision. Capacity planning sizes resources, deployment automation ships code, and incident triage handles live failures.
Question 5Architect Fundamentals and the CTA Journey
A stakeholder insists a new integration must be available even if a single data center fails. Which architect fundamental does this requirement most directly drive?
- Resilience and availability design Correct answer.
- User-interface theming
- License cost optimization
- Source-code formatting standards
Explanation
Surviving a data-center failure is a resilience and availability concern, so the architect designs redundancy and failover accordingly. Theming, code formatting, and license optimization do not address failure tolerance.
Question 6Architect Fundamentals and the CTA Journey
Which of the following is an example of a non-functional requirement an architect must capture?
- The system must send a confirmation email
- The system must let users reset their password
- The system must display an order history page
- The system must support 5,000 concurrent users with sub-second response Correct answer.
Explanation
Non-functional requirements describe qualities such as performance, scalability, and reliability rather than specific behaviors. Concurrent-user load with a response-time target is a quality attribute; the others are functional behaviors.
Question 7Architect Fundamentals and the CTA Journey
An architect is choosing between a monolithic and a microservices architecture. Which consideration is most characteristic of the architect's decision?
- Deciding the color scheme of the admin console
- Weighing trade-offs such as deployment independence against operational complexity Correct answer.
- Selecting the team's preferred code editor
- Choosing the length of variable names
Explanation
Architectural decisions are about trade-offs among qualities such as deployability, scalability, and operational burden. Editor choice, console colors, and naming conventions are implementation details far below the architectural level.
Question 8Architect Fundamentals and the CTA Journey
What is the primary purpose of a well-architected framework pillar such as security or reliability?
- To guarantee zero defects in production
- To replace the need for requirements gathering
- To prescribe a single vendor product for every workload
- To provide guiding principles and design questions for evaluating a solution Correct answer.
Explanation
Framework pillars organize guiding principles and review questions that help architects evaluate and improve designs. They are vendor-neutral guidance, not product mandates, and they complement rather than replace requirements work.
Question 9Architect Fundamentals and the CTA Journey
A client wants a solution that is easy to evolve as business needs change. Which design principle should the architect emphasize?
- Tight coupling between all components
- Loose coupling with clear interface contracts Correct answer.
- Hard-coding business rules in the user interface
- Maximizing shared global state across modules
Explanation
Loose coupling with explicit interface contracts lets components change independently, which supports evolution over time. Tight coupling, embedded rules, and shared global state all increase the blast radius of change.
Question 10Architect Fundamentals and the CTA Journey
Which activity belongs to the 'design' phase of a solution lifecycle rather than the 'operate' phase?
- Scaling capacity in response to live traffic
- Responding to a production alert
- Defining component boundaries and data flow Correct answer.
- Applying a security patch to a running server
Explanation
Defining component boundaries and data flow is design work that precedes implementation. Patching, alert response, and live scaling are all operational activities performed after the system is running.
Question 11Architect Fundamentals and the CTA Journey
An architect maps a customer's journey from first awareness of a product through purchase and support. What is this map used for?
- To replace the system architecture diagram
- To calculate the licensing cost of the platform
- To identify touchpoints, pain points, and required capabilities Correct answer.
- To determine the programming language for the backend
Explanation
A customer journey map reveals touchpoints and pain points that translate into required capabilities, bridging business context and architecture. It does not replace a technical diagram, choose languages, or compute license costs.
Question 12Architect Fundamentals and the CTA Journey
Which of these best describes a 'stakeholder' in the context of architect fundamentals?
- Exclusively the software developers on the team
- Any person or group with an interest in or influence over the solution Correct answer.
- Only the external auditors of the organization
- Only the end users of the finished application
Explanation
Stakeholders include anyone affected by or able to influence the solution, such as sponsors, users, operators, and auditors. Limiting the term to users, developers, or auditors alone misses the breadth of the concept.
Question 13Architect Fundamentals and the CTA Journey
A solution must handle a tenfold traffic spike during a seasonal sale without manual intervention. Which quality attribute is most relevant?
- Data durability
- Localization
- Auditability
- Elastic scalability Correct answer.
Explanation
Automatically absorbing a large, temporary traffic increase is elastic scalability. Durability concerns data persistence, auditability concerns traceability of actions, and localization concerns language and regional adaptation.
Question 14Architect Fundamentals and the CTA Journey
When documenting an architecture decision, why does an architect record the alternatives that were rejected?
- To satisfy a requirement that all documents exceed a page count
- To assign blame if the decision later fails
- To lengthen the document for appearance
- To preserve the rationale and constraints so future teams understand the choice Correct answer.
Explanation
Recording rejected alternatives captures the context, constraints, and reasoning behind a decision, which helps future maintainers avoid revisiting settled questions. It is about shared understanding, not document length or assigning blame.
Question 15Architect Fundamentals and the CTA Journey
Which statement best captures the relationship between architecture and technical debt?
- Architecture decisions can create or retire technical debt and should account for it Correct answer.
- Technical debt disappears once the system is deployed
- Technical debt is only a coding concern with no architectural dimension
- Architecture and technical debt are unrelated concepts
Explanation
Architectural choices such as technology selection or integration style can accumulate or reduce technical debt, so architects must weigh long-term maintenance costs. Debt is not confined to code and does not vanish on deployment.
Question 16Architect Fundamentals and the CTA Journey
An architect is told a legacy system must be replaced but cannot be taken offline during business hours. Which approach best reflects sound architectural reasoning?
- Design an incremental migration with parallel running and rollback Correct answer.
- Ignore the constraint and schedule a daytime switchover
- Perform a big-bang cutover at midnight without a fallback
- Delay the project indefinitely until a full outage is allowed
Explanation
An incremental migration with parallel running and a rollback path respects the no-downtime constraint while managing risk. A big-bang switchover, indefinite delay, or ignoring the constraint all increase the chance of disruption.
Question 17Architect Fundamentals and the CTA Journey
Which of the following is the clearest example of a functional requirement for a payment system?
- The system must process a card payment and return an authorization result Correct answer.
- The system must be available 99.95 percent of the time
- The system must respond within 200 milliseconds
- The system must encrypt data at rest
Explanation
Processing a payment and returning a result is a specific behavior the system must perform, making it functional. Availability, encryption, and response time are quality attributes that constrain how behavior is delivered.
Question 18Architect Fundamentals and the CTA Journey
In the CTA journey, what typically distinguishes the 'Associate' or intermediate stage from the Awareness stage?
- It requires no further study beyond the Awareness material
- It adds deeper domain knowledge and applied scenario practice Correct answer.
- It focuses exclusively on marketing content
- It removes the need to understand architect terminology
Explanation
Progression beyond Awareness adds depth: more detailed domain knowledge and applied scenario practice that build toward advanced architect work. The later stage does not discard terminology, eliminate study, or focus on marketing.
Question 19Architect Fundamentals and the CTA Journey
An architect proposes adding a caching layer to reduce database load. Which trade-off should be explicitly acknowledged?
- Cached data can become stale, so consistency must be managed Correct answer.
- Caching removes all need for performance testing
- Caching eliminates the need for a database entirely
- Caching always increases database load
Explanation
Caching improves read performance and reduces database load but introduces staleness risk, so the architect must define consistency and invalidation strategy. Caching does not remove the database, increase load, or eliminate testing.
Question 20Architect Fundamentals and the CTA Journey
Which practice best supports traceability from business goals to technical components in an architecture?
- Keeping all design decisions in individual memory
- Relying on verbal agreements only
- Documenting components without linking them to goals
- Maintaining a requirements-to-design mapping Correct answer.
Explanation
A requirements-to-design mapping shows how each component serves a business goal, which supports impact analysis and review. Verbal agreements, unlinked component lists, and undocumented memory all break traceability.
Question 21Architect Fundamentals and the CTA Journey
What does 'separation of concerns' mean as an architect design principle?
- Combining all responsibilities into one module for simplicity
- Splitting a system into parts that each address a distinct responsibility Correct answer.
- Ensuring every component handles every concern
- Removing all interfaces between components
Explanation
Separation of concerns divides a system so each part focuses on a distinct responsibility, improving clarity and maintainability. Merging responsibilities, removing interfaces, or making every component handle everything does the opposite.
Question 22Architect Fundamentals and the CTA Journey
A stakeholder asks why the architect created a context diagram before detailed design. Which answer is most accurate?
- To select the cloud region for hosting
- To finalize the deployment pipeline configuration
- To show the system's boundaries and its interactions with external actors Correct answer.
- To fix the exact database schema immediately
Explanation
A context diagram establishes scope by showing the system boundary and its external actors and systems, guiding later detail work. Schema, pipeline, and region choices come later and at a finer level.
Question 23Architect Fundamentals and the CTA Journey
Which scenario best demonstrates an architect applying risk-based thinking?
- Choosing technologies solely by personal preference
- Treating all requirements as equally critical regardless of impact
- Avoiding all documentation to save time
- Prioritizing design effort on components whose failure would most damage the business Correct answer.
Explanation
Risk-based thinking directs attention and rigor toward components where failure has the greatest business impact, balancing effort against consequence. Treating everything equally, skipping documentation, or choosing by preference ignores risk.
Question 24Architect Fundamentals and the CTA Journey
Which of these is a legitimate reason for an architect to choose a managed cloud service over a self-managed equivalent?
- To avoid any need for security configuration
- To reduce undifferentiated operational burden while retaining control where needed Correct answer.
- To eliminate all operational responsibility and cost
- To guarantee the service will never fail
Explanation
Managed services reduce undifferentiated heavy lifting such as patching and scaling, letting the architect focus on differentiating concerns while still configuring security and controls. They do not remove all responsibility, guarantee uptime, or eliminate security work.
Question 25Architect Fundamentals and the CTA Journey
An architect is asked to justify a design to both technical and non-technical stakeholders. Which approach is most effective?
- Avoiding any discussion of trade-offs
- Framing the design in terms of business outcomes alongside technical rationale Correct answer.
- Presenting only low-level code snippets to everyone
- Using jargon to demonstrate expertise
Explanation
Effective architect communication connects technical choices to business outcomes and openly discusses trade-offs, making the design accessible to varied audiences. Code-only detail, jargon, and hiding trade-offs alienate non-technical stakeholders.
Question 26Architect Fundamentals and the CTA Journey
In the CTA journey, which outcome most clearly marks a candidate's transition from Awareness into the Associate stage?
- Leading a formal design review board for enterprise systems
- Publishing original architecture case studies reviewed by peers
- Recognizing that solution architecture is a distinct role and wanting to learn what it involves Correct answer.
- Earning a foundational credential that validates hands-on platform configuration skills
Explanation
Awareness is about recognizing the discipline exists and building interest in what the role entails; the move toward Associate begins when that interest becomes structured learning and skill validation. Publishing case studies or chairing design boards are later-stage behaviors tied to demonstrated practice, not early awareness.
Question 27Architect Fundamentals and the CTA Journey
An architect is preparing a solution overview for executives who control funding. Which content choice best fits that audience while remaining consistent with architect fundamentals?
- A runbook describing on-call escalation steps for production incidents
- A schema listing of database indexes and partitioning keys
- A detailed sequence diagram of service-to-service calls during checkout
- A cost, risk, and business-outcome summary mapped to the decisions executives must approve Correct answer.
Explanation
Architect communication is audience-calibrated: decision-makers need the business outcome, cost, and risk framing tied to the choices only they can authorize. Technical artifacts such as call sequences, index schemas, and runbooks serve engineers and operators, not funding approvers.
Question 28Architect Fundamentals and the CTA Journey
An architect is defining the boundary of a new billing capability inside a larger platform. Which artifact most directly establishes what is inside that boundary versus what it depends on from outside?
- A capacity plan projecting transaction volume growth over three years
- A release calendar sequencing deployment windows across teams
- A context diagram showing the billing capability, its actors, and external systems it interacts with Correct answer.
- A test strategy listing unit, integration, and acceptance coverage
Explanation
A context diagram is the standard tool for fixing scope: it names the capability, its human and system actors, and the external interfaces crossing the boundary. Capacity plans, test strategies, and release calendars operate within an already-defined scope rather than defining it.
Question 29Architect Fundamentals and the CTA Journey
A team proposes splitting a customer capability into four independently deployed services so each can scale on its own. Which consequence should the architect weigh most seriously before endorsing the split?
- Independent deployment removes the need for interface contracts between the services
- Cross-service consistency and operational overhead grow, so the split pays off only if independent scaling and release cadence are genuinely needed Correct answer.
- Each service automatically inherits stronger security controls, so the split reduces overall risk
- Splitting always lowers total cost because each service consumes fewer resources
Explanation
Decomposition trades a simpler in-process consistency model for distributed coordination, observability, and deployment overhead, so it is justified only when independent scaling or release autonomy is a real requirement. Security posture, interface contracts, and aggregate cost are not automatically improved by splitting.
Question 30Architect Fundamentals and the CTA Journey
Midway through delivery, an architect learns that a regulation will require customer data to remain in-country within six months. Which response best reflects sound architect judgment?
- Silently relocate all data stores to a single in-country region without informing stakeholders
- Continue the current design and defer any analysis until the regulation takes effect
- Revisit the architecture decisions and constraints, assess the blast radius on data placement and integration, and record the change with its rationale and residual risk Correct answer.
- Add the requirement to the backlog as a low-priority item for the operations team
Explanation
Architecture is a continuing cycle: new constraints trigger reassessment of decisions, impact analysis across affected components, and explicit documentation of rationale and residual risk. Deferring, downgrading, or acting without stakeholder visibility all break the traceability and governance the role exists to maintain.
Question 31Data Modeling and Data Management
In a Salesforce data model, which relationship type creates a lookup field on the child object that does not require a value and does not cascade delete records?
- Lookup relationship Correct answer.
- Hierarchical relationship
- Master-detail relationship
- Many-to-many relationship
Explanation
A lookup relationship creates a loosely coupled link: the child's lookup field can be left blank, and deleting the parent does not delete the child. Master-detail instead makes the child's field required and cascades deletion. Hierarchical relationships are self-lookups on User, and many-to-many is implemented with a junction object rather than a single relationship type.
Question 32Data Modeling and Data Management
Which statement accurately describes the role of an external ID field when importing records with the Data Import Wizard or Data Loader?
- It automatically enforces uniqueness across all objects in the org.
- It is a custom field marked as an external ID that lets you match incoming rows to existing records during upsert. Correct answer.
- It is required on every object before any import can run.
- It stores the Salesforce 15-character record ID for matching during upsert.
Explanation
An external ID is a custom field flagged as External ID that holds a value from an outside system; during upsert, Salesforce uses it to decide whether to update an existing record or insert a new one. It is not the Salesforce record ID, uniqueness is not enforced org-wide by default, and no object requires one for ordinary inserts.
Question 33Data Modeling and Data Management
A data architect needs a field that automatically calculates a value from other fields on the same record and is never edited directly. Which field type should be used?
- Formula field Correct answer.
- Picklist field
- Roll-up summary field
- Text field with a validation rule
Explanation
A formula field derives its value at display time from an expression referencing other fields on the same record and cannot be edited by users. Roll-up summaries aggregate child records on a master-detail parent, a validation rule blocks saves rather than computing values, and a picklist only offers predefined choices.
Question 34Data Modeling and Data Management
Which Salesforce feature is designed to prevent duplicate records from being created by users or by API inserts?
- Field-level security
- Duplicate rules Correct answer.
- Sharing rules
- Validation rules
Explanation
Duplicate rules compare incoming or edited records against matching rules and can block saves or alert users when a duplicate is found. Validation rules enforce data quality conditions unrelated to matching, sharing rules control record access, and field-level security controls field visibility and editability.
Question 35Data Modeling and Data Management
What is the primary purpose of a junction object in a Salesforce schema?
- To hold formula calculations for a single object.
- To replace master-detail relationships with lookups.
- To store audit history for a parent record.
- To implement a many-to-many relationship between two objects. Correct answer.
Explanation
A junction object carries two master-detail (or lookup) relationships, one to each of two objects, which models a many-to-many association such as products and price books. It does not store audit history, replace relationship types, or exist to hold formulas.
Question 36Data Modeling and Data Management
Which data management capability does the Salesforce Data Loader provide that the Data Import Wizard does not?
- Deduplicating records during import.
- Mapping CSV columns to fields.
- Scheduling exports and processing very large record volumes via the command line. Correct answer.
- Importing accounts and contacts from a CSV file.
Explanation
Data Loader is a client application that supports command-line and scheduled operations and can process large record volumes, including export and delete operations. The Data Import Wizard also imports accounts and contacts, offers deduplication, and lets users map columns, so those are not differentiators.
Question 37Data Modeling and Data Management
Which statement best describes a record type in Salesforce?
- It defines the set of picklist values and page layouts presented to a group of users for an object. Correct answer.
- It stores the external ID used for upsert operations.
- It controls which users can log in to the org.
- It determines the sharing model for the entire org.
Explanation
Record types let one object present different business processes by pairing picklist values and page layouts with profiles. They do not govern login access, store external IDs, or set the org-wide sharing model.
Question 38Data Modeling and Data Management
A company stores customer addresses in a single text field and now needs to filter and report by country. Which data modeling change best supports this requirement?
- Create a separate Country picklist or lookup field and populate it from the existing address data. Correct answer.
- Add a formula field that extracts the country from the address text.
- Add a validation rule that requires the address field to be non-empty.
- Increase the address field length to 255 characters.
Explanation
Filtering and reporting by country requires the country to be its own structured field so it can be indexed, filtered, and grouped. Extracting with a formula depends on fragile text parsing, extending the text field does not separate the data, and a validation rule only enforces presence.
Question 39Data Modeling and Data Management
An architect needs a roll-up summary of opportunity amounts on the account. Which prerequisite must be satisfied?
- The opportunity must have a master-detail relationship to the account. Correct answer.
- The opportunity must have a lookup relationship to the account.
- The account must be the parent in a many-to-many junction.
- The opportunity amount field must be a formula field.
Explanation
Roll-up summary fields are available only on the parent side of a master-detail relationship, so the child opportunity must be master-detail to the account. A lookup does not support roll-up summaries, many-to-many is irrelevant here, and the aggregated field need not be a formula.
Question 40Data Modeling and Data Management
A data steward wants to ensure that every account record has a billing country before it can be saved. Which mechanism enforces this at the data layer?
- A validation rule on the Account object Correct answer.
- A sharing rule on the Account object
- A page layout that marks the field required
- A report filter on billing country
Explanation
A validation rule is evaluated on every save, including API inserts and updates, and can block records missing a billing country. Page layout requirements apply only to the UI, sharing rules govern access, and report filters affect only report output.
Question 41Data Modeling and Data Management
During an upsert with Data Loader, which field must be specified so that Salesforce can match incoming rows to existing records?
- An external ID field Correct answer.
- The CreatedDate field
- The OwnerId field
- The record's Name field
Explanation
Upsert requires an external ID field (or the record ID) to determine whether each row matches an existing record. Name is not guaranteed unique, OwnerId identifies a user, and CreatedDate is a system audit field that cannot serve as a matching key.
Question 42Data Modeling and Data Management
A schema has Account, Contact, and a custom object Enrollment with master-detail relationships to both Contact and Course. What does this model represent?
- A many-to-many relationship between Contact and Course. Correct answer.
- A one-to-one relationship between Contact and Course.
- A lookup-only relationship between Contact and Course.
- A hierarchical relationship on the User object.
Explanation
Enrollment acts as a junction object with master-detail relationships to both Contact and Course, which implements a many-to-many association. It is not one-to-one, not a User hierarchy, and not a lookup-only link.
Question 43Data Modeling and Data Management
Which statement about the Salesforce schema builder is accurate?
- It is the only place where validation rules can be created.
- It visually displays objects and their relationships and allows adding fields and relationships. Correct answer.
- It replaces the need for profiles and permission sets.
- It automatically normalizes all custom objects to third normal form.
Explanation
Schema Builder is a graphical tool that shows objects, fields, and relationship lines and supports creating fields and relationships directly. It does not normalize data, manage user permissions, or monopolize validation rule creation.
Question 44Data Modeling and Data Management
A consultant needs to prevent users from deleting accounts that have related opportunities. Which configuration achieves this?
- Make the opportunity-to-account relationship master-detail. Correct answer.
- Set the account sharing model to Private.
- Create a formula field on Account that counts opportunities.
- Add a validation rule on Opportunity that blocks deletion.
Explanation
With a master-detail relationship, the parent account cannot be deleted while child opportunities exist, which prevents the deletion. Validation rules on Opportunity do not block parent deletion, sharing settings do not prevent deletes, and a counting formula does not enforce anything.
Question 45Data Modeling and Data Management
Which data quality technique best addresses inconsistent country values such as 'USA', 'U.S.', and 'United States' in an imported dataset?
- Creating a separate object for each country variant.
- Storing the country in a long text area field.
- Standardizing values against a controlled picklist or reference table before load. Correct answer.
- Loading the values as-is and relying on users to correct them later.
Explanation
Standardizing values against a controlled list before loading ensures consistent reporting and filtering. Loading inconsistent values defers the problem, a long text area does not constrain values, and creating objects per variant worsens the model.
Question 46Data Modeling and Data Management
A team wants to ensure that a custom object's records are owned by users and can be shared through the role hierarchy. Which relationship configuration supports this?
- A lookup relationship to the parent object Correct answer.
- A master-detail relationship to the parent object
- A hierarchical relationship to the User object
- A self-referential lookup on the custom object
Explanation
Records on the child side of a lookup relationship have their own owner and participate in sharing, so the role hierarchy applies. Master-detail children inherit ownership from the parent and do not have independent sharing, while hierarchical and self-referential lookups do not provide this ownership model.
Question 47Data Modeling and Data Management
Which statement correctly describes how field-level security interacts with page layouts?
- Field-level security controls record access, while page layouts control field access.
- Page layouts override field-level security so users always see all fields placed on the layout.
- Field-level security determines whether a user can see or edit a field, while page layouts determine where visible fields appear. Correct answer.
- Field-level security and page layouts are the same configuration stored in one place.
Explanation
Field-level security governs field visibility and editability for a user, and page layouts arrange the fields that the user is permitted to see. Layouts do not override field-level security, the two are separate configurations, and record access is controlled by sharing rather than field-level security.
Question 48Data Modeling and Data Management
A data architect is designing an object to store line items for an order. Each line item must be deleted when its order is deleted and must not exist without an order. Which relationship should be used?
- Many-to-many junction between line item and order
- Lookup relationship from line item to order
- Hierarchical relationship from line item to order
- Master-detail relationship from line item to order Correct answer.
Explanation
A master-detail relationship makes the parent required and cascades deletion of children, matching the requirement that line items cannot exist without an order. A lookup allows orphans, a hierarchical relationship applies to User, and a junction models many-to-many rather than a strict parent-child dependency.
Question 49Data Modeling and Data Management
Which consideration is most important when choosing between a formula field and a roll-up summary field for a numeric value on a parent record?
- Both field types can aggregate child records identically.
- Formula fields can aggregate child records, while roll-up summaries cannot.
- Neither field type can reference other fields.
- Roll-up summaries aggregate child records, while formula fields calculate from fields on the same record. Correct answer.
Explanation
Roll-up summary fields aggregate child records across a master-detail relationship, whereas formula fields compute from fields on the same record. Formula fields cannot aggregate children, the two are not interchangeable, and both can reference other fields.
Question 50Data Modeling and Data Management
Which practice best supports a reliable data migration into Salesforce?
- Skipping field mapping and letting Salesforce guess column meanings.
- Running a test load in a sandbox and validating record counts and field mappings before production. Correct answer.
- Loading all records in a single pass without validation.
- Importing directly into production without a backup.
Explanation
A sandbox test load validates mappings, transformations, and record counts before production, reducing the risk of corrupt data. Single-pass loads without validation, skipped mappings, and unbacked production imports all increase the chance of errors.